Comments
To help us better understand your suggestion, please answer the following questions:
1) Could you describe how you are ingesting the data from Dynamics 365 Sales into CI: What's the data structured like in CI?
2) You mention the functionality "projected attributes": This is available for segments, but it doesn't work on the Customers entity. What problem were you hoping to solve with projected attributes?
Independent from your answers, I'm sharing the product team's goals regarding using CI data in Dynamics 365 apps:
Customer insights’ goal is to offer an effortless way to surface its valuable data in Dynamics 365 apps and Power Platform. The Customer Insights card add-in has no GA date, because most customers are transitioning to use the data through the Dataverse that provides additional customization options. This means Dataverse with its connectors and API are the sustainable consumption service. For time being, the card add-in is our out-of-the-box solution for showing some Customer Insights data in Dynamics 365 apps.
Note: I appreciate you can restrict delivery options based on country - however this generates a poor customer experience, where they enter their delivery address details first, only to find out the order cannot be delivered to their address. The error message in this instance, doesn't even prompt the customer that the reason is that their country is not available for any delivery option.
I expect that the above should already be working us such. The journal line order should not have an impact on the success of posting.
It does not make sense, as line numbering is not "posting date"-dependent hence should not affect behavior.
If that is the case, it seems that the result of the "Transfer all posting errors to a new journal" functionality is dependent on a random factor, that being, the journal line number.