Hi,
I am building an SSIS project to transfer data from CRM Online and from an internal web application into AX 2012 database.
During the import I experienced the following problem:
While the records are imported successfully into AX 2012, I receive an error message whenever I try to create the same type of records from the UI, which persists until I delete the imported records. From what I read it is related to RecId duplication (apparently the system is trying to create the record's row with the same RecId that I used during the import).
I followed this article below to try to update the NextVal field of the SYSTEMSEQUENCES table (where the next RecIds for each table are kept), but I still receive this error.
https://sumitsaxfactor.wordpress.com/2011/04/01/handling-recids-in-sql-server/
Can you suggest me any other approach through which I can manage the RecIds and avoid the problem I described?
I have also read that I can "reserve" certain number of RecIds through using X++ code and then calling the X++ service in my SSIS project, still I am trying to avoid that approach for the moment, as we want to keep the logic "SSIS only" as it would be easier for the other .NET Developers in the team, who are unfamiliar with AX 2012 and X++, to support it, as it's pure C# and SQL code for the moment.
Yet, if there is no feasible way to use only SSIS to fix this issue, what else would you suggest me to use?
Thanks.
Best Regards,
Evgeni Dyulgerov