Expand my Community achievements bar.

SOLVED

FORMS AEMaaCS CRM Dynamics - multiple entities submit

Avatar

Level 10

Hello all,

 

I have a custom form data model annd associations. A custom data source to MS Dynamics CRM. I have a form with 15 tables to submit in one go and with error handling for each put/post. 
These tables are in a parent child relationship. Submitting parent did not submit child data although PUT request for parent has child entity. Surprising!
hence trying multiple puts 


Question - how do i submit to all tables in multiple put/posts. Submitting to parent entity via PUT api does not update child and is stunning to me. 

 

OOTB one entity can be submitted via FDM submit, I can handle via workflows but does not show up errors to the user in page so defeats the purpose. 



@mayankg @workflowuser 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

 

You are rite OOTB only one entity can be submitted, and Workflow or custom submit action with Dermis Bridge API can handle support mulitple entity.


I can handle via workflows but does not show up errors to the user in page so defeats the purpose.

 


Is there a particular reason you want to show errors to the end-user (form filler)? If all validations are in place, there should be nothing for the end-user to change to fix the submission issue. In fact, using AEM workflows is much better as administrators or backend personas can see the reason for the failure and retrigger the process if required.

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Hi,

 

You are rite OOTB only one entity can be submitted, and Workflow or custom submit action with Dermis Bridge API can handle support mulitple entity.


I can handle via workflows but does not show up errors to the user in page so defeats the purpose.

 


Is there a particular reason you want to show errors to the end-user (form filler)? If all validations are in place, there should be nothing for the end-user to change to fix the submission issue. In fact, using AEM workflows is much better as administrators or backend personas can see the reason for the failure and retrigger the process if required.