Dynamics CRM metadata broken due to missing EntitySet owners

[davidmoten]

As mentioned in #51 this is not a problem with odata-client but rather a problem with Dynamics published metadata in that generating code fails due to the missing EntitySet owners. This link suggests that the owners EntitySet path is for internal (to Microsoft) use. In that case it seems like the appropriate action is to add an empty EntitySet owners to the metadata.

[davidmoten]

I suspect this problem with the metadata will stick around so I might add an option in the odata-client-maven-plugin to handle missing EntitySets by auto-creating empty EntitySets if there is one referenced. Something like <autoCreateEntitySets>true</autoCreateEntitySets>...

[davidmoten]

Might be better to optionally drop NavigationPropertyBindings which have a target (EntitySet) that does not exist. For the plugin: <failOnMissingEntitySet>false</failOnMissingEntitySet>.

[davidmoten]

option to ignore this problem with bad NavigationPropertyBinding Target added to odata-client-maven-plugin in master, closing for now on the assumption that owners is for internal use in Microsoft. Discussion continuing at https://stackoverflow.com/questions/63984862/why-is-the-entityset-owners-not-present-in-dynamics-crm-metadata/63991650?noredirect=1#comment113189327_63991650