Thank you Sossah.
Just for other issue to migrate ...what was your procedure to "migrate" . Packout from 3.7 or manually from pssql migrate table and then window.. ?
I have the code.
You have to migrate the whole instance to idempiere, preferably latest release. Remember you have to run generate uuid process to take care of all new custom tables. Then you packout. I think we need to create a repository to work on the code so we can also add new things. Its not entirely a smooth process though.
Anthony, I deleted the attachment as packing in causes data corruption on iDempiere.
The official IDs that are present on the PackOut.xml are not officially taken from the developer.idempiere.com site and collides with other elements already assigned.
was used for AD_Role.IsAccessAdvanced
in the packin this element comes for C_SalesStage_UU and then the role table is corrupted as the column is renamed.
I think maybe this was caused if you ran the generate uuid process with "Dictionary Maintenance" enabled and the sysconfig key "DICTIONARY_ID_USE_CENTRALIZED_ID" set to N.
As I see this combination must be forbidden - maybe we need to validate this combination on iDempiere and stop the sequence generation as it's a lead to data problems.
I'm attaching file IDEMPIERE-1265.patch with the corresponding migration scripts.
I'm attaching file IDEMPIERE-1265_2.patch, this patch contains all changes and files necessary for that correct functioning.
Here are the links to the documentation of adaxa to better understand how it works that new feature.