The real problem is that this happens in the first place when things change. I'm not sure if a warning for an optional attribute is the answer, it means that just a single call to a CreateEntity with a lot of optional attributes will generate a pile of useless warnings, further degrading True Change's value. (Mandatory attributes get errors now, at least). At the same time... yes, this OFTEN causes severe, silent runtime errors and it takes intensive testing to notice it.

J.Ja

I fully agrea with Justin.  To many warnings could make them less  efective

Best Regards

If too many warnings are an issue for you (versus a unknown defects by missing mappings), then please adjust this idea such that this feature can be turned off/on  as a setting available to in the Service Studio Preferences fields.

If you ever wanted to search an for an empty Attribute Mapping, there is no way in ServiceStudio to do such a thing except manually clicking on every object that has a property.

I have never set any attributes as mandatory on in structures which is the developers primary domain for non scaffolded applications.

 I see the issue more with:

1. Aggregates to Business Objects
2. Business object casting
3. Mapping Generic Actions/Structures to/from a Business Object.