With Normal Dimension say for (Category and Category Values) its pretty simple to use the out of the box FCM configuration to add associate Property Values to Dimension Values as we know, what will be the values coming for the Category Dimension.
But I am not able to visualize how it can be done for other Dimensions which is Autogenerated but getting created from FCM.
Can anyone please share some possibilities, I would be really thankful.
Here's one sample scenario to help you visualize how FCM can be used.
Let's assume that your source system has an intention details table with three columns: Partnumber, Intention Name, Intention Value
You can use FCM (PCI) to generate the corresponding Dimensions using the data in this table. Additionally, you can also have FCM generate the corresponding Dimension Values, though it's not always required. If FCM is being used to generate Dimension Values as well, then all dynamically generated dimensions will need to be marked as non-autogen (attribute.dimension.autogen=false).
When FCM's Configuration Generation Forge runs, it modifies the pipeline files after they're copied to the data\processing folder. It creates the new dimensions, dimension values and dimension mapping in the pipeline. The mapping that gets generated would be like:
Source: Intention Name, Target: Intention Name
For example, Source: Screen Size, Target: Screen Size
When you read in the data in the main pipeline, you'll get the SKU details from one table and the corresponding intention details from the other table. Add a record manipulator after the Record Adapter which reads the intention details. Use this record manipulator to create a new property where the Property Name = Intention Name and Property Value = Intention Value. Join the SKU data from the first table with the intention data, on Partnumber and enable multi sub-records.
What this would result in is that each record will have multiple additional properties, in addition to the standard attributes. These additional properties will represent an intention-intention value pair each.
The FCM will create the dynamic dimensions mapping at runtime, so you don't need to touch the Prop Dim Mapper for this.
I hope this helps.