Nicolas Saleron Cap Vision

Hello,

All French company with more than 152 500 euros have to declare the CVAE (Company Value Added Contribution).

The rules are expressed here: https://entreprendre.service-public.fr/vosdroits/F23546

It would be a good improvement to support this kind of statement in standard as this is an horizontal regulatory and not industry specific.

In NAV 2018, we got demo data in the CRONUS company for French localization for FR Acc. Schedule Name and Payment Slips features.

These demo data are not in Business Central anymore making it difficult for new consultants to setup the modules in new deployments.

Could you bring back these settings?

When you setup the new intrastat feature in France, it creates the Data Exchange Definition named "INTRA-2022-FR".

Inside the Line Definition 2-SENDER, there is two column definitions:

• /Party[@partyType]
• /Party[@partyRole]

These attributes are always exported with an empty value (which is rejected by authorities) because the "Export If Not Blank" field is not checked.

Could you fix this issue in next releases so the deployment of the new intrastat feature will be easier for partners and customers?

With Business Central 2025 wave 1, Microsoft will be able to delete obsolete tables and fields from their own apps.

Publishers on AppSource are facing the same issues as Microsoft: our products evolve, our products are sometimes redesigned.

We need at some point to break things (= deleting tables and fields).

My thought is that we are conscious of the consequences of deleting customer data and we are already following the obsoletion pattern.

If a table or field is deleted, and Microsoft want to ensure we are not doing this too quickly, the apps could be compared to a version published X months ago and ensure this table/field is already ObsoleteState = Removed at that time.

With Business Central 2025 wave 1, we gain the ability to prevent FlowFields from being calculated if they are not visible in a page.

Sometimes, we add customizations where variables are displayed as fields, especially in lists.

For instance, it is not rare to add the availability of an item in the Item List.

Computing such field might be time consuming, and end users are not particulary happy if we propose to create a dedicated page for such fields. However it could help user who does not use these fields to be less impacted by them.

This idea proposes to allow a developer to discover if a field visible on the client page.

For instance:

field(MyField; MyFieldWithTimeConsumingComputation)

{

}

...

trigger OnAfterGetRecord()

begin

 if CurrPage.Controls.MyField.IsVisible() then

   //MyFieldWithTimeConsumingComputation := ...;

end;

The function IsVisible() would take in account all customizations.

If the property Visible of the field is set with a variable in AL code, it would return the current value of the property.