Can you point at the earlier post on the forum? I'm not entirely sure I understand your problem. But it looks like you have validation on an entity in your domain model and you're also exposing this entity and the actual values do not match with your validation rules, am I correct? In this case you could create some API entity instead and expose that in your web service. An alternative could be to map to your attribute using a microflow to avoid setting incorrect values.
Hi Mohammed, we're facing the same behavior and solved it by creating a webservice module with temporary objects. These temporary objects are exposed in our webservice and after a webservice call we try to map the temporary object to a real object. Before we do that, we'll do all sort of validations. If the call is not correct, we send feedback back to the caller with a long string of validations results. We use this approach in all kinds of webservice, because it's much more save and you're in control.
I would avoid exposing real objects in a webservice, because you want to validate things first, before you create objects in your database. This is only when you do complex things, for simple operations you can always expose your real objects.