'The field AccountNum is not present in source' - error in DMF after mapping done successfully

(0) Share

Report

Posted on by Community Member

Hi,

can someone please help me with an issue I am running into while trying to import customers using the newest DXIF? I have done the mapping successfully and was able to generate the preview of the source file - all looking good.

Then when I am trying to run the job to get the staging data, I get this error message: 'The field AccountNum is not present in source'. But it is and it has been mapped successfully, checked both the source and the target mapping.

The vendor upload works beautifully, only seem to be having this issue with the Customer entity.

Has anyone seen this before?

Thanks!

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (1)

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

Like (0)

Report

Hi Katjusa,

Check if you have some empty lines at the end of your source file. This could cause the error.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for the suggestion Andre!

It is a CSV file and I have regenerated it numerous times, just checked it again, no empty lines...

Could it be something else causing the error?

Was this reply helpful? Yes No
André Arnaud de Cal... 301,075 Super User 2025 Season 2 on at

Like (0)

Report

Hi Katjusa,

Can you try to import the first number of lines e.g. create a file with only 10 customers?

You can also temporary set the mandatory property on this fieldnum in the staging table (DMFCustTableEntity) to no. Then all lines should be imported. If it will give an error on another mandatory field you can repeat it for that field again.

Then you can see what really happens with the contents of the file.

Can you also confirm that the AccountNum field in the preview is still filled? Otherwise the settings might be overwritten.

Was this reply helpful? Yes No
aahmednafea 135 on at

Like (0)

Report

Hi There,

For the AccountNum field, what is the setup for the field in the Modify Source Mapping form? are you generating the account num automatically from the number sequence?

regards,

Ahmed

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Andre,

unfortunately I cannot set the AccountNum temporarily to non-mandatory, as this is a primary key and the system does not allow me to change it from mandatory.

Thanks,

Kata

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Ahmed,

thanks for the reply. No, I am not generating them automatically, I am trying to push in manual values into the AccountNum. I first thought maybe I had to set the number sequence for the CustAccount to manual, but then I realized it was set to manual, so that should not be the cause of the problem.

The AccountNum is set to Auto-generated = 'no' on the source mapping, also 'Auto-default' = 'no'

Thanks,

Kata

Was this reply helpful? Yes No
aahmednafea 135 on at

Like (0)

Report

Hi Kara,

Can you send me the source file on ahmadnafi3@hotmail.com as I would like to have a look at it?

Cheers,

Ahmed

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Ahmed,

I will replace the actual client information in the file with fake data and will send it to you later today!

Thank you very much for your help in advance!

Kata

Was this reply helpful? Yes No
André Arnaud de Cal... 301,075 Super User 2025 Season 2 on at

Like (0)

Report

Hi Katjusa,

Normally the primary key should be unique and mandatory. In this case for testing I would change the field property and probably also change the primary key (temporary). Of course only when there is no data yet available in this table. When everything is working again, then bring the table to the original state.

You can also use the debugger to see when this error occurs and so find out the cause. You need to have some development skills then.

If you want, you can also sent me the sample file. You can find my mail address in my profile.

Note that changing the data in the file can have other outcomes, also the setup in our environments could be different, but it is worth to give a try.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Andre,

the DMF doesn't let me set the AccountNum to not mandatory.

Unfortunately I suspect that the problem is not in the source file. I have regenerated not just the source file itself with the data, but the source file format using the DMF entity several times. Then I have put different records from the customer's long list of data in there, to see if the problem was with the data - repeated it several times. I have deleted and recreated the processing group in the DMF numerous times as well. To me, this sounds like the issue might be related to the 'Customer' entity itself in the DMF.

I agree that at this point, there is nothing else to do than to put in a break point and try to figure out where is the problem coming from. I don't code, so I'll have to get a developer involved. Which is what I was trying to avoid by creating this thread in the first place (sigh...)

Just one last question; we are running R2 CU6, but have updated the kernel and installed the latest DMF version. Could it possibly come from some kind of mismatch between CU6 and the new DMF code? Has anyone had experience with it?

Thank you!

Was this reply helpful? Yes No