• Published
  • M2M Fall 2019 Release Notes

    Release Date: November 2019 | Version Name: Fall 2019 | Version Number: 1.2

     

    New Features

    Filter which records are displayed in a tagging component 

    When creating a tag setting, users can now determine if any records should be filtered out to reduce the list of tags displayed in the dropdown list. This can be achieved using:

    1. Fields on the object itself 

    2. Fields on child objects 

    Guided screen to create a new tag setting record

    A simplified setup process now helps users create a new tag setting record! 

    When a user clicks creates a Tag Setting and opens the new record, a screen displays to guide them through the setup process, including: 

    1. Dynamic display of a dropdown list of all standard and custom objects in the system 

    2. Depending on the object selection, dynamic display of a dropdown list of fields on the selected object

    🛈 Upgrade Note: Due to this new interface, it is recommended that only the Tag Setting Name and Archive Mode field are left on the Tag Setting page layout, and all other fields are removed.

    Print related record names into long-text rollup fields

    On both catalog and target objects, Many2Many can now leverage long-text fields to concatenate the labels of related records that are generated through the component. This enhances a user’s ability to filter and customize list views on these object records, based on any related records.


    Resolved Issues

    Clearing an invalid search cleared the number value for “Add Selected (#)”

    If a user has selected at least one tag and then uses the search bar to find a potential tag which results in an invalid result, clearing out the search query results in the previously selected tag not being recognized. 

    This is now resolved to ensure that onClear of the invalid search query, 

    • Selection of the tag is retained (i.e. the display is “Add Selected (#)” rather than “Add Selected ()”

    • onClick of Save, junction record corresponding to the selected tag(s) are created  

    Tagging multiple records on the same object requires a manual page refresh

    If a user creates a new tag on Record 1 on Catalog Object 1, and then goes to Record 2 for the same object to create a new tag, they are unable to do so without manually refreshing the page for the second record. It was noted that any kind of interaction with the Many2Many component in the first record causes the component on any subsequently opened record (of the same object) to not work. 

    This was reported when navigating between different records of the same object. i.e. this can be replicated when navigating between two Contact records, but not when navigating from one object to another. 

    This is now resolved so that a user can add tags for different records of the same object. 


    Configuration Updates

    New fields to store filter logic 

    1. API Name: Catalog_Filter_Logic__c

      1. Type: Long Text

      2. Contains: Filter Logic (SQL query for fetching display list)

    2. API Name: Target_Filter_Logic__c

      1. Type: Long Text

      2. Contains: Filter Logic (SQL query for fetching display list)

    New fields to map long-text roll-up fields

    1. API Name: Catalog_Object_Rollup_Field__c

      1. Type: Text(255)

      2. Contains: API Name of long-text roll-up field on catalog object for concatenation

    2. API Name: Target_Object_Rollup_Field__c

      1. Type: Text(255)

      2. Contains: API Name of long-text roll-up field on target object for concatenation