Dynamics Community Forum Thread Details

Hello BF-02041229-0,

You've accurately described a common limitation with SubGrids in Dynamics 365 forms when you uncheck "Show Related Records" and try to add new records. The native behavior indeed breaks the parent-child relationship mappings when you move away from the "Show Related Records" functionality.

Let's break down the situation and explore solutions:

Understanding the Problem:

"Show Related Records" Functionality:
- This option automatically filters the SubGrid to display records related to the parent record.
- It also automatically populates lookup fields on new child records with the parent record's ID.

Custom Filters:
- When you apply custom filters to the SubGrid, you're essentially overriding the "Show Related Records" functionality.
- This means that the automatic parent-child mapping is lost.

New Record Creation:
- When you click the "+" button to add a new record from the SubGrid, the system doesn't automatically populate the lookup field that links the child record to the parent record.

Solutions:

Custom Ribbon Button and Xrm.Navigation.openForm (Recommended):
- Concept:
  - Create a custom ribbon button on the SubGrid that opens the child entity's form using Xrm.Navigation.openForm.
  - Pass the parent record's ID as a parameter to the form.
  - Use JavaScript to populate the lookup field on the child record form with the parent record's ID.
- Implementation:
  1. Create a JavaScript Web Resource:
    - Create a JavaScript web resource in Dynamics 365.
    - Add the following JavaScript code:
    function openChildRecordForm(executionContext) {
    var formContext = executionContext.getFormContext();
    var parentRecordId = formContext.data.entity.getId();
    var parentRecordEntityName = formContext.data.entity.getEntityName();
    var relationshipName = "your_relationship_name"; // Replace with your relationship name
    var childEntityName = "your_child_entity_name"; // Replace with your child entity name
    var lookupFieldName = "your_lookup_field_name"; // Replace with your lookup field name
    
    var formParameters = {};
    formParameters["_CreateFromId"] = parentRecordId;
    formParameters["_CreateFromType"] = parentRecordEntityName;
    formParameters["_CreateFromRelationship"] = relationshipName;
    formParameters[lookupFieldName] = {
    id: parentRecordId,
    entityType: parentRecordEntityName,
    name: formContext.data.entity.getAttribute("name").getValue() // Or other parent record name
    };
    
    Xrm.Navigation.openForm({
    entityName: childEntityName,
    parameters: formParameters
    });
    }
    - Replace the placeholder values (your_relationship_name, your_child_entity_name, your_lookup_field_name) with your actual values.
  2. Use Ribbon Workbench:
    - Use the Ribbon Workbench to customize the SubGrid's command bar.
    - Remove the default "+" button.
    - Create a new custom button that calls your JavaScript function (openChildRecordForm).
  3. Publish Customizations:
    - Publish your customizations.
- Advantages:
  - Provides full control over the new record creation process.
  - Ensures that the lookup field is populated correctly.
  - Works with custom filters.
- Disadvantages:
  - Requires JavaScript development.
  - More complex implementation.

Business Rules (Limited):
- Concept:
  - You could attempt to use a Business Rule on the child entity's form to set the lookup field value when the form is loaded.
  - However, this might not work reliably if the parent record ID is not passed to the form.
- Limitations:
  - Business rules are primarily designed for form field manipulation, not for controlling SubGrid behavior.
  - This method is not recommended.

Power Automate Flow (Less Direct):
- Concept:
  - Create a Power Automate flow that's triggered when a new child record is created.
  - The flow would retrieve the parent record ID from the triggering record and update the lookup field.
- Limitations:
  - Requires an extra step after the child record is created.
  - Not as seamless as a ribbon button.
- Advantages:
  - No JavaScript development required.
- Disadvantages:
  - Not as user friendly.

Recommendation:

Custom Ribbon Button and Xrm.Navigation.openForm (Option 1) is the recommended approach. It provides the most reliable and direct way to ensure that the lookup field is populated correctly when adding new records from a SubGrid with custom filters.

By using the JavaScript customization, you can effectively address the limitation of parent-child relationship mappings when using custom filters in SubGrids. Remember to test thoroughly and consider the user experience.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Using SubGrid setFilterXml without Show Related Records - Mappings not working

Helpful resources

Quick Links

Ramesh Kumar – Community Spotlight

Congratulations to the June Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates