Configure Many2Many Junction Object(s)
This page covers:
Related pages:
Junction Object Configuration
Installing M2M for Amp Impact? Visit this page to dig into the junction object configuration guidance for Amp Impact.
Functionally, M2M creates a junction record between two records of different objects. To use M2M, you may configure your objects in several ways (outlined below). The Tag Settings object, highlighted in red, is installed as part of the package.
From these object models, you can see that you'll need a many-to-many relationship between the two objects you want to use for tagging. This can be achieved through a separate junction object.
Select one or any combination of the above object models based on the system’s overall data model. Many2Many supports both models, so you can make a decision based on reporting needs and/or object limitations.
When creating the junction object, check that the user permissions are in place to allow users to view and add tags to the relevant records.
Name Field
The junction object’s Name field must be set as an Auto-number field. This allows automatic tagging without errors. Alternatively, if you set the Name Field on the junction object as a Text field, you will need additional custom development to ensure that the Name populates correctly on the creation of each new record.
Lookup to Tag Settings
Create a lookup relationship between the junction object and the Tag Settings Object.
Archive Mode
If you decide to use Archive Mode on your tags, you will need to create two Date Fields on the junction object(s):
Tag Date: This field will populate with the date when a tag is added through the component and Archive Mode is enabled. If a tag is removed and then added again, this field will re-populate with the most recent add date.
Archive Date: This field will populate with the date when a tag is removed through the component and Archive Mode is enabled. If a tag is removed and then added again, this field will become blank until the tag is again removed.