Comments
Setup should be consistent, As per new design registration number stands for e.invoice, all customers must setup registration number.But most reports are working with Siret number on vendor / customer card.The Siret number on REgistration number should be copied on customer/vendor card to avoid customization or manual work.
please put some priority on this. after some further universalcode testing, I concluded its not possible to query onprem table 2000000207 "Application Object Metadata" from a target=cloud app (not even when using recordrefs). Because of this, we have a gap with the capabilities in table 2000000038 AllObj, table 2000000058 AllObjWithCaption, and table 2000000136 "Table Metadata" that I'm hoping this BC Idea will address
We have similar situation, were a customer is using Variants and Intercompany flow. Now we did some extra development to cover the issue, but it was an unforeseen development.Also if this suggestion would be considered, please also take in mind the new Cross-environment intercompany. Because at this moment, this functionality can't be changed trough development because the API is non extensible and there are no publishers.
I support this idea!Implementing this would provide real added value and help us to ensure performance for the customer and efficient utilisation of resources for the platform.Together with the ideas mentioned in this topic, the analysis and handling of indexes would be greatly improved.To summarise, these would be:improve page "Database Missing Indexes"add a new page "Database Index Usage"add a new custom dimension to telemetry event RT0005: "Used SQL Index"