on
RE:
Since Microsoft has found a way to clean up standard Business Central apps, the next logical step would be to allow third parties to do the same—ideally, at the same time during the Step version update. Currently, many tables, schemas, and even some Enums are awaiting removal. For example, if an Enum is used in a field, the field cannot be removed, which in turn prevents the removal of the Enum.
RE:
Hello,Has anyone been able to obtain feedback from Microsoft on this idea?Is it still on the road map or not ?Thank you in advance for your help !
RE:
This is absolutely needed. 10 digits are just not enough, as written already.
RE:
Heading to 7years and no option.. which is crazy is that you can conditionally change the... background but not values
RE:
Referring to this document, I believe most users expect it to work this way:https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-analytics
RE:
I fully agree with this post. Over time, table and field ranges will fill up with Removed tables and fields, which not only adds needless baggage to the app, but also make the app less maintainable. Microsoft has already conceded that point, and they are planning a cleanup in BC26 (2025 RW1).There will need to be some rules for this, as there are for existent breaking changes. You will need to have published at least X version(s) with the removed field/table in order to give extending apps time to update their data.
RE:
Same issue here. To say this is disappointing is an understatement.
RE:
Maybe can add a dax formula in the slicer to automatically select current month/last month/current year/last year, etc.It should be pretty basic as almost everything can be derived from TODAY()
RE:
A more common use case could be when you search for "Year". Almost all models have a plain "Year" column in their date table. Many model also have lost of time intelligence measures like "Sales Previous Year" and similar. Being able to get better control of the reult of the filtering would be really helpul. Especially when working on large and breoad models.
RE:
Thank you very much for your reply! First of all, it's a known limitation that Scheduler doesn't support CI/CD, but we're working on it. CI/CD for Scheduler will be supported in three dimensions: Git, deployment pipeline, and public API. The experience will be consistent with other current CI/CDs. This feature is expected to go live on 3.31, and we'd love to hear from you then.