-
Possibility to add relations on views
Allow the possibility to create relations on views to other tables. This will make sure relations are automatically done when using these views in forms, so the joins will be handled by metadata and not to be added by developer by overwritting the init method off a datasource.
When using extensions this would limit the code that has to be written, because you can only overwrite a datasource init by creating a new class and using an event handler
-
Possibility to directly create union statement in view
The possibility to directly create union statement in view instead of first creating a query object and assigning the query to the view
-
Code Coverage
It would be nice if we could see code coverage come back in 365 for operations. By specifying unit tests to see which parts of the code are covered by these tests.
-
Support images in Tree control
please bring back the possibility to include images in tree items.
When creating a new FormTreeItem, one can include an image or overlayerimage. But the platform is not doing anything with that.
So would be nice if we could use our own resources or symbols.
-
Custom BP extensions and the build process
Custom BP extensions should be installed in <drive>AosService\PackagesLocalDirectory\Bin\BPExtensions to be picked up. Currently during build, you have to write a custom script to copy them from the workspace to the correct location. This could be improved possibly
-
Remove the default "new comment" label comment
Please remove the default "new comment" comment when creating a new label. It can be empty by default
-
API for setting up Electronic reporting
In the electronic reporting module you can import configurations from Microsoft through LCS repository. This is now done through UI and the classes are marked internal. We would like to have an API to call this through automation. So an API to create a repository and an API to import configurations from a repository.
-
Introduce AOT table property to disable lock escalation
In production environments sometimes lock escalation is disabled on certain tables to reduce locking on multi threaded batches. It would be handy if this could be set as a proprety on a Table in the AOT. The data base synchronisation process could then disable/enable by default, so no db maintenance scripts are needed anymore -
Introduce a property on a table field to set a default value on SQL
It would be nice to have a property on a table field which defines the default clause on the SQL table, now 'empty' values are used as default values. This enables more metadata driven development, so no need for coding anymore. for example now it's generating ALTER TABLE [dbo].[CUSTGROUP] ADD DEFAULT ((0)) FOR [BANKCUSTPAYMIDTABLE] or ALTER TABLE [dbo].[CUSTGROUP] ADD DEFAULT ('') FOR [CLEARINGPERIOD] or ALTER TABLE [dbo].[CUSTINVOICETABLE] ADD DEFAULT ('1900-01-01 00:00:00.000') FOR [CORRECTEDINVOICEDATE_RU] It would be nice to have an influence on that default clause. For example changing the default value for a date to current date or so.
You’re offline. This is a read only version of the page.
