No way to filter very large metadata files

[The-Futurist]

I can't see any way to restrict the generated code to some subset of entities. I have metadata that generates a 1.3 million line C# source file and we only care about a handful of entities. The filter option seems to be there but is always unpopulated:

Can you tell me if this is a bug or there's something I must do to see that list get populated (it could just be so big that the code fails to populate it).

By the way, here's the metadata, if you test with it, it might expose a subtle bug (just rename it from .txt to .xml)

$metadata.txt

This is not my metadata by the way, its from a huge API supported by Anthology corporation.

[ChristianPardun]

@KorporalKernel
What I have done for these scenarios is to develop a custom OData.Model.Generator. This can be set externally, e.g. which entities etc. and then this generator creates a new model metadata file containing only the necessary entities and their dependencies. At the end I use the new file to feed the Unchase service.

[The-Futurist]

@KorporalKernel What I have done for these scenarios is to develop a custom OData.Model.Generator. This can be set externally, e.g. which entities etc. and then this generator creates a new model metadata file containing only the necessary entities and their dependencies. At the end I use the new file to feed the Unchase service.

That's quite imaginative, a good idea actually especially with an insanely large metadata file like the one I'm using. Is the code open source? I toyed with making an OData validator (which would have reported this entity name error) but struggled as I wasn't sure on where the DTDs etc were for all this.

[The-Futurist]

I think what could be hugely helpful is to add a new checkbox option to this page:

named Create separate source file for each namespace or something.

Then instead of me seeing a 1.3 million line huge source file, I'd see a bunch of files that contain everything for just their namespaces.

It could take a namespace like Cmc.Nexus.Regulatory1098T.Helpers.Reports and generate a source file named Cmc_Nexus_Regulatory1098T_Helpers_Reports perhaps (or just leave it as dots)

[The-Futurist]

Actually the ConnectedService.json file supports an option to generate multiple files, named "GenerateMultipleFiles": true but it has no effect on your extension and in fact the extension seems to remove the option when I build the code...

These options are documented here:

https://learn.microsoft.com/en-us/odata/connectedservice/reference#config-file-json

[ChristianPardun]

@KorporalKernel What I have done for these scenarios is to develop a custom OData.Model.Generator. This can be set externally, e.g. which entities etc. and then this generator creates a new model metadata file containing only the necessary entities and their dependencies. At the end I use the new file to feed the Unchase service.

That's quite imaginative, a good idea actually especially with an insanely large metadata file like the one I'm using. Is the code open source? I toyed with making an OData validator (which would have reported this entity name error) but struggled as I wasn't sure on where the DTDs etc were for all this.

Unfortunately its not public nor open source. Maybe I can thing about.

Is your metafile available? If so I can try to feed my Generator with it and see what happend!? 😀 Never have such a hugh file.

[The-Futurist]

@KorporalKernel What I have done for these scenarios is to develop a custom OData.Model.Generator. This can be set externally, e.g. which entities etc. and then this generator creates a new model metadata file containing only the necessary entities and their dependencies. At the end I use the new file to feed the Unchase service.

That's quite imaginative, a good idea actually especially with an insanely large metadata file like the one I'm using. Is the code open source? I toyed with making an OData validator (which would have reported this entity name error) but struggled as I wasn't sure on where the DTDs etc were for all this.

Unfortunately its not public nor open source. Maybe I can thing about.

Is your metafile available? If so I can try to feed my Generator with it and see what happend!? 😀 Never have such a hugh file.

Sure, here it is:

$metadata.txt