Hi ALll,
Since the EmpExpense table, EmpExpenseNum is required sequentially, so I want to change its data type from INT to NVARCHAR(8). Is it safe if I do it?
Definitely don’t do that.
I know it is dangerous. But I review some other table primary key like AP invoice. the InvoiceNum column data type is nvarchar as well. Just curious if we could make them work similarly.
Why on earth would you want to change the data type of a primary key in an Epicor table? It makes zero sense…
Not sure what you’re trying to accomplish
We want to do mass import employee expense to Epicor, if I use DMT or updatable dashboard, I have to know each employee expense number. because in Epicor, it is required to be sequentially and continuously, it is hard to search each employee expense number.
I am just thinking may be if I change data type from INT to nvarchar, then it is not necessarily to make expense number continuously.
For example, now in Epicor. the expense number is generated auto-increment for each employee level, I want to make it on company level.
Like Jose had mentionned before…
If you modify Epicor tables, this will void your support and further upgrades probably…
As in other areas we found that some designs were not standardized amongst the different groups developping this application… not just tables but GUI as well…
Pierre
Left image is Epicor logic now, Right side is the goal I want.
Is any idea how I could accomplish it?
Thanks all, I need a brain storm.
Dear Xiaoting Geng,
The way Epicor processes table key numbers is central to proper software processing of transactions. However, you can easily create a UD field (or in E9 use one of the already-available user fields) to contain your user information; then you can use the numbers for whatever purpose you need.
Best
…Monty.
1 Like