You’re offline. This is a read only version of the page.
Hi,
I created a custom entity and entered records in the conversion table (Data migration framework/Processing Group/Entities/Modify source mapping/Mapping details/Conversion) but during "Get Staging Data"/Ascii->StagingEntity the conversion table seems to get ignored.
The conversion feature works fine for out of the box entities. I tested it with the CustomerEntity. During "Get staging data"/Ascii->StagingEntity the values in the source fail were successfully converted according to my entries in the table "DMFStagingConversionTable". (The conversion is allready triggered in the preview!)
I wonder if it is necessary to add some source code somewhere. I was looking at the source code of the class "DMFCustomerEntityClass" and the Staging Table "DMFCustomerEntity" but I was not able to find anything related to conversion.
thx for your help!
*This post is locked for comments
@FH-Inway: thx for your reply. Could you go into more detail please
@skaue: It seems that more people have exposure to that tool and the community starts to give more feedback on DMF related issues. I will install DMF to my latest R2 image and try to recreate my scenario.
You are right about the name of the column not being a dependency, and it should convert regardless of whatever you call it. I must admit I have created several custom entities and all my conversions are working as expected. I am running Beta 2.
mapping field names != mapping field values
thx for your reply.
It is a while ago and working with that tool was very tedious. Probably due to its beta status. Currently I do not have access to the above environment.
BUT if what you say is true, than i do not see the point to have a mapping table in the first place. Why bother to map if the name of the source field and target field must be equal?!
Hi Kim
You've probably fixed this by now, but for whomever reads this, the reason your first example did not get the conversions applied is the column header being wrong in the source file. Instead of "wmsLocationId", it should have had "plant_code". That is what your source definition says, as far as I can see. And the conversion logic looks for that column in the source, as far as I know, and will replace values according to your specification.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,902
Super User 2024 Season 2
#2
Martin Dráb
229,316
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (