...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Junction Object Configuration
| Info |
|---|
Installing M2M for Amp Impact? Visit this page to dig into the junction object configuration guidance for Amp Impact. |
...
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.
You should select Select one or any combination of the above object models based on the system’s overall data model. Many2Many currently supports two both models, so you can make a decision based on reporting needs and/or object limitations.
One important consideration when When creating the junction object is , check that the user permissions that need to be 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. OtherwiseThis allows automatic tagging without errors. Alternatively, if you set it the Name Field on the junction object as a Text field, you will need additional custom development for to ensure that the Name to populate populates correctly on the creation of each new record.
Lookup to Tag Settings
You must create Create a lookup relationship between your 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 Date Fields on your 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.
...