Product Configuration with ODATA Service
I just at the start of a new implementation of a product configurator with ODATA Services and I have a general question regarding the architecture .
My problem is that I am not sure how to desing my data model in a way it reflects my requirements.
Of course I can design a model that represents a product with the corresponding characteristics and values but the complicated part for me is how to reveice the validation of a configuration (like constraints and text input validaton) out of the serice as I do not want to soruce the logic out to the client application.
The point is that I have a mixture between static data (characteristic textes and values...) and the dynamic validation information that depends on the current configuration represented in the client.
So my question is: can I somehow implement a READ Operation that receives the current configuration as a parameter (not key) and returns the characteristicValueSet with the information if they are still valid or not to the client?
I also thouth about implementing special Actions in my service like getCharacteristicWithValidationBasedOnConfiguration and passing the configuraton from the client but i hope that there is smarter solution for this.
As you recognize I am quite new to ODATA so please be clement
Looking forward to your suggestions.