Error SCM-120011 on Delivery Preview | Community
Skip to main content
Prasanna_Soni
Prasanna_Soni
Level 4
February 23, 2022
Solved

Error SCM-120011 on Delivery Preview

  • February 23, 2022
  • 3 replies
  • 1634 views

Error while evaluating document

SCM-120011 The value 'none' of element 'Additional fields (extraField)' is not a valid reconciliation operation (document with schema 'deliveryMapping')

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Prasanna_Soni

Issue Resolved. It was Data issue in which length of field in XML data Schema is not set to INT64 so that resulted with temp table creation with INT32. As soon as we fixed the data schema , issue got resolved 

3 replies

Tobias_Lohmann
Adobe Employee
Tobias_LohmannAdobe Employee
Adobe Employee
February 24, 2022

Hi,

can you please add more details? Where exactly do you see this message? Is this for every delivery on your system or for specific only? 

Thanks and best regards, Tobias

Prasanna_Soni
Prasanna_SoniAuthorAccepted solution
Level 4
February 28, 2022

Issue Resolved. It was Data issue in which length of field in XML data Schema is not set to INT64 so that resulted with temp table creation with INT32. As soon as we fixed the data schema , issue got resolved 

    P
    Poonam_Dogra
    Level 4
    March 31, 2022

    Hi @prasanna_soni ,

    Thank you for sharing the solution, it would be helpful if you could please explain which field the length needs to be adjusted? Or was it a random custom schema field which was supposed to be int64 but got missed?

    Facing the same issue while creating a new delivery  and selecting any of the target mapping except the default mapping- nms:recipient.

    Thanks in advance!

    david--garcia
    david--garcia
    Level 10
    February 28, 2022

    In the failing deliveryMapping, you may have the value of 'none' in the additional fields tab, this should actually be mapped correctly. if you are not sure, go through each custom mapping and check which one has the 'none' value and remove that. and test again, perhaps it was left by mistake.

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...