Extension field only visible in first table in dunning letter

[kostadin_terziev]

Hello community,

We have extended Dunning business object with a field which shows the invoice number for Bulgaria. We have added it to the form and bound the table items like this: $.bulgarianInvoiceNumber_3RNKO6KPNZTCGIUQNQZWR7IQO_Y02KGS5GY In the first table of the dunning letter print form the column with the number is filled with our extension field, but in the second table it is blank. I noticed that the first table uses data connection with Dunning>ReceivableItem>DunningItem while the second table uses Dunning>ReceivableItem>ReminderItem.

In output history in the dunning screen i viewed the xml data message and i saw that in tag DunningItem we have our extension field while in tag ReminderItem it doesn't exist. However in Cloud Application Studio there is only one Item node and there is no separation like in the print form and in Adobe Livecycle Designer. Can you tell me where does this separation happen and where the Item node is divided into DunningItem,ReminderItem, NonDueItem? How can we display our extension field in all those divisions of the Item node? Regards, Kostadin

[ayechan]

Hi @kostadin_terziev,

Did you find out the solution of this issue?

I also face the same issue.

So, If you found out the solution, could you please share with me the information?

Best Regards,

Aye Chan

[kostadin_terziev]

@ayechan As far as I remember, I had to open a case with SAP.

Then they added the field in the other nodes as well.

[ayechan]

Hi @kostadin_terziev,

Understood!

And thank you very much for your prompt reply.

If I create a case in development tenant and sap teams added that custom field in development tenant,

is that custom field auto carried to another nodes of test tenant and PRD tenant?

Best Regards,

Aye Chan

[kostadin_terziev]

@ayechan I believe not, but best to consult SAP for that.

[ayechan]

Hi @kostadin_terziev, Thanks for your information! I will consult with sap teams.