From what I understand, when we create a custom attribute on the EBOM (Physical Product) and it corresponding Provided Part custom attribute initially they don't talk to each other.  Meaning that when I update the attribute on in the EBOM I want the value to reflect on the provided Part based on it's assigned Product.

I believe you have to create some business logic in the form of an EKL script and store it in the Dataset-Up

Can anybody provide a simple example of the EKL Business logic that needs to be in place within the Dataset-up and where would I store this within the Dataset-Up?

Where can i find the Documentation, or Does somebody have some they can share?

Example:

Physical Product-------------------------> Assigned Product ----------------------> Provided Part

     Instance                                                                                                             Instance

            NKLA_EBOM_StaticTorque - Real --------------------->EKL?------------------------>NKLA_MID_StaticTorque - Real                                                                                      

     Reference                                                                                                           Reference

            NKLA_EBOM_Coating - Real -------------------------->EKL?-------------------------->NKLA_MID_Coating - Real   

Thanks

Marc

Update 06/20/2024

I was able to find the Entry Point in Dataset Up, but this seems to be Only After the Creation of the Implementation Link, how do i maintain value changes between the EBOM and MBOM?