Hi, following up with others here. The main issue from Microsoft's side is that this framework is built on DLLs which means building a API to communicate with this external solution is probably not an easy task to accomplish. One other issue is that the framework requires a order line reference to complete the configuration. This means that the API would then have to get called against or generate the order line in the same operation, which is not always possible if the order is created in one transaction scope. Based on this a "general" API to solve the configuration seems like a hard task to complete.In my current project we've built an integration solution that runs during sales order creation and accepts configuration attribute values from an external source and maps it to several product configuration models through XML parsing. The code handles configuration on several models even though only one is associated to the sales order line. This however requires the reference being set to the sales order line for all configurated items even though they are configured attached from the main component (not utilizing the sub-component relation). It's not a pretty solution but is works. Why this is important to keep pushing is for Microsoft to actually put some effort in improving the solution and hopefully making it easier to use in code rather than doing XML parsing to solve the case. This is broadly used by customers and many rely on this framework. A framework that is this important should be easier to implement and improve.