Hi,
I'm curious what the integrations teams view is on this. I recently noticed this warning (I think it is a new addition to the docs)
Now when using the BC oData v4 BluePrints, especially when dealing with variants this gets quite tricky. A lot of BC implementations use dots or dashes in notations for Item_No. In the mappings below is an example where Item_No is mapped to productId, which in many cases will not work in conjunction with the above of keeping ProductId strictly alphanumeric.
Any plans to update the blueprints to deal with this in some way?
