FORMS AEMaaCS CRM Dynamics - multiple entities submit | Community
Skip to main content
Level 9
June 13, 2024
Solved

FORMS AEMaaCS CRM Dynamics - multiple entities submit

  • June 13, 2024
  • 1 reply
  • 452 views

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. 



@mayankgu9 @workflowuser 

 

 

 

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 Vijay_Kumar_Jalagari

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.

1 reply

Vijay_Kumar_Jalagari
Adobe Employee
Vijay_Kumar_JalagariAdobe EmployeeAccepted solution
Adobe Employee
June 25, 2024

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.