DIXF Route entity not approving.

(0) Share

Report

Posted on by Community Member

Hi All.

Undergoing a data migration and can see that the route version flag doesn't import using the standard template / entity.

Looking at the mapping, the source field 'approved' is put into staging, then goes nowhere.

Does anybody know whether...

1) There is any system constraints surrounding this (there is a logical sequence to approving a route).
2) Is there any reason why I cannot retrospectively update the db using tsql? (i.e. does the approved flag update any other areas of the system?)

My reseller has a real downer on updating directly in the database, which I understand, but with my previous experience it is often the fastest way to resolve simple issues.

Thanks

2012 R2 CU7

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

It is possible that the flag is overwritten on the insert command. I don't know if you enabled the option to execute business logic on the processing groups or not.

You can also check the target entity mapping if the approved field is mapped from staging to target or not.

About direct SQL statements: I'm also not a fan, but I do agree in some cases it is the best/fastest solution. There used to be a fill utility in AX which could also mass update records. This has been depreciated. Microsoft recommends to use SQL scripts for simply updating some fields on existing records. Direct inserts is NOT recommended. Have also a look at the next page for the statement about updating using SQL: technet.microsoft.com/.../dn527189.aspx

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

Thanks for the response.

I can confirm that the approved field is not mapped from staging to target.

I was proposing running through the DIXF process, then simply running a global update statement as all route versions will be approved on go live anyway.

Also, business logic was selected, just for info.

Thanks

Was this reply helpful? Yes No
Suggested answer

5400 7,162 on at

Like (0)

Report

Hi,

Staging to direct target mapped is not required for this field because it will come from generate method. please check your file column field "Route_Approved" is set as "yes" or not.

Note: please check your target mapping "Route_Approved" field should be link with GenerateRouteLink function.

If it is set as yes, it will get updated with method \Classes\DMFRouteEntityClass\GenerateRouteLink() automatically.

Please check and confirm.

Thanks

Bhaskar

Solution architect.

Blog: ax2012dixf.blogspot.com

Was this reply helpful? Yes No
5400 7,162 on at

Like (0)

Report

Hi,

I want to add one more points. I had describe previouse commnets for route_Approved field. Hope it is working fine. In case of route version approved field should be auto mapped by default untill you did not have any customization. please check your file data should be 0/1 or Yes/No. It should work. Hope this field is not mapped with other any function.

Mapping : Stgaing Approved --> Traget Approved.

Thanks

Bhaskar

Was this reply helpful? Yes No
Carlos B on at

Like (0)

Report

Hi,

just a quick tip:

when you are dealing with updating approval and active checks you have an easy way to check if all it is correct. You have to make the change to one route and then try to use it manually. if it Works then you have done the change properly.

It seems quite obvious but in this case there are not several implications and need another more complex scenarios to test, if it Works manually then it is correct. i´m only refering to these checks not about the integrity of the route

Best Regards,

Carlos B.

Was this reply helpful? Yes No