67

Add possibility to extend OnFindRecord and OnNextRecord triggers on pageextension objects

Could you please add possibility to extend OnFindRecord and OnNextRecord triggers on pageextension objects? Currently it is not supported. But this are very useful and powerfull triggers, which developers often use. Sometimes it is the only way to use this triggers to add needed cusom logic to a ...

Read more...

3 Comments

Read more... 3 Comments

Category: Development (1162)

STATUS DETAILS
Needs Votes
Ideas Administrator
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team
66

Re-enable multi-level tree list support in Webclient (ShowAsTree / IndentationControls)

Windows client provided support to build 'dynamic' pages using collapsing tree views. Collapsing / expanding tree nodes was userfriendly, since it limits the information shown when loading the page and allows to user to decide on what node / level information was needed. However, since the mov...

Read more...

2 Comments

Read more... 2 Comments

Category: Development (1162)

STATUS DETAILS
Completed
Ideas Administrator
Good news! We released this feature as part of 2020 Release Wave 1.

Please refer to the following link for more information:

Best regards,
Mike Borg Cardona
Program Manager, Microsoft
65

AppSource validation for previous versions should compare against the latest available

With every major release, there comes a period where sometimes we need to publish apps on the store in two different versions: one which uses events and features only present in the new major, and one which is still compatible with the old major.


This is because customers have...

Read more...

3 Comments

Read more... 3 Comments

Category: Development (1162)

STATUS DETAILS
Completed
Ideas Administrator
Thank you for this suggestion! Since early December 2023 we have validated AppSource app hotfixes against the latest version on the next targeted major/minor Business Central

65

Ability to suspend and restart Code Analysis

When developing in a big workspace and/or in a big single-folder solution it is not always helpful to have the code analyzed as You go. - Code Analysis will often be slow to react - Code Analysis will be surfacing errors and warnings not related to what You are actually doing at the moment So t...

Read more...

2 Comments

Read more... 2 Comments

Category: Development (1162)

STATUS DETAILS
Completed
Ideas Administrator
Thank you for your feedback. We have been investing a lot in the code analyzer framework this upcoming 2023 release wave 1. You can already try it out in the Preview release.

We have optimized when rules are run, fixed some inefficiencies, and disabled rules no longer run…

We have also introduced a new “File” scope for code analysis during authoring , so that code analysis now runs on the active file only by default. This provides much better .performance during coding with, and most rules rely on local analysis anyway. You can still enable rules to run on project level, as they also all run on full build

The benefits are that workspace size does not prevent the use analyzers​ and thus analyzers can be enabled in larger apps and used for everyday work, and you do not need to wait on the CICD pipeline build for CodeCop errors.​

In addition, we've added a new code analyzer performance statistics output, you can enable it via the `outputAnalyzerStatistics` setting. This provides a summary of time spent per rule. Use it to discover which rules are actually running, as well as low-performing rules, in order to enable/diable rules during authoring.

On a related note, you can now also use urls in al.ruleSetPath as well as in includedRuleSets path in the the ruleset file. This makes it easier to share, maintain and enforce common rules

Best regards,
Business Central Team
64

New system virtual table suggestion - Application Field Metadata

Table 2000000207 "Application Object Metadata" can be used to determine what extension app a table lives in. However, there is no such virtual table at the field level. If I want to know what app “owns” a field (either in a table object or a table extension object in an app), there are no system...

Read more...

2 Comments

Read more... 2 Comments

Category: Development (1162)

STATUS DETAILS
Needs Votes
Ideas Administrator
Thank you for your feedback. We are considering adding it to our longer term roadmap, please keep voting for this.

We have a related request to include extension origin in IntelliSense for a field. That is inline while developing, but would not support querying (for VSIX extensions) or see all fields for a given extension, what is more useful?

Your help is greatly appreciated,
Business Central Team

64

Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Would like to see that the AL compiler or one of the code analyzers gives a warning when the Get procedure is called with insufficient arguments, too many arguments, or arguments of invalid types that do not match the formal parameters expected given the PK of the record in question. This is an e...

Read more...

4 Comments

Read more... 4 Comments

Category: Development (1162)

STATUS DETAILS
Needs Votes
Ideas Administrator
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.

Best regards,
Business Central Team
63

"Go to definition" more than once when you are in the base App

When we are using "Go to definition" it works fine as long as I am moving in my own objects. When I use "go to definition" on a "Base App" or "System App" object, a .dal-file is opened, which is fine in the first place, but in many cases I want to navigate through other objects of the Base/System...

Read more...

0 Comments

Read more... 0 Comments

Category: Development (1162)

STATUS DETAILS
Completed
Ideas Administrator
Thank you for your valuable feedback. We have decided to deliver this idea and make it available with Business Central 2020 Wave 2, as well as Business Central 2020 Wave 1 CU2

Up until now Go-to-Definition (F12) has relied on retrieving sources from server, and to support multiple configurations, we added  a defaultLaunchConfigurationName setting to indicate which connection to use. This caused unwanted side-effects, so we have restructured F12 to rely on local dependency applications for resolving the source of a reference symbol for apps with runtime versions >= 5.2 (2020 Wave 1 CU2).

This implies that DAL file symbol source navigation support multiple steps/depth as long as symbols are present. There is no support for going a step back again though, i.e., Alt+Arrow Left will go back to starting point. Also, note that F12 will use local symbols which might not reflect server versions - this is relevant when using F12 to navigate into, e.g., a referenced extension to set breakpoints.

For versions <= 5.2 Go to Definition will work as before defaultLaunchConfigurationName, i.e., no source file for reference symbols on a Go to Definition if more then one debug configuration is defined.

Your help was greatly appreciated,  
Peter Borring
PM, Microsoft  

62

Copy link functionality in Business Central for temporal pages is missing

After building a temporary custom page - working with base application tables we have identified that the copy link button cannot be used accordingly as opening the link gives an error message.


If the page is being opened through the search bar and Copy link functionality is ...

Read more...

2 Comments

Read more... 2 Comments

Category: Development (1162)

STATUS DETAILS
New
62

TableExt Default SQL Join Behavior

Currently, we need to use SetLoadFields to define, if fields will be excluded from a FindSet/Get. This leads to extending necessity the Base App or other base solutions to prevent performance issues.


When creating a TableExt, setting a default value for each field would give u...

Read more...

1 Comments

Read more... 1 Comments

Category: Development (1162)

STATUS DETAILS
New
62

Missing enum functionalities which are absolutely necessary in the dynamic development

In the daily programming the handling of the newly introduced enumerations and enum extensions is not exactly conclusive. I think the idea is generally good, but unfortunately there are some essential points missing: 1. impossible dynamic use with RecordRef and FieldRef: So far it is impossible...

Read more...

6 Comments

Read more... 6 Comments

Category: Development (1162)

STATUS DETAILS
Under Review
Ideas Administrator
Thank you for your feedback. We are considering adding it to our longer term roadmap.

Your help is greatly appreciated,
Business Central Team