Best Of
Re: Whether it is possible to use a debugger to understand from what place object are call?
Indeed you can but it will only tell you from where your break occurred, not all. If the page can be called from multiple places then you may not know where else may be referring to it. On the other hand, there's an app called NAVCore Objects Manager that will help you find all references to the page or objects. It may not be perfect since it can't find dynamically referenced objects such as reports that are defined as part of a report selection but it does a pretty good job of finding objects referenced in code. Take for example the Sales Order page, it can be referenced by more than a dozen other objects.
Tony_NCD
6
Re: Whether it is possible to use a debugger to understand from what place object are call?
Thanks for the great information. It looks like there are similarities with Stati c/al Prism which also offers some of the functionalities you mentioned.
Re: Deep insert in API page problems
Hi Skollops,
in your docker url you are using the API endpoint, in your BC online url you are using the ODataV4 endpoint (this endpoint does not support deep inserts)
try changing
https://api.businesscentral.dynamics.com/v1.0/{{tenant}}/{{environment}}/ODataV4/Company('{{company2}}')/salesReturnOrder?$expand=items
to
https://api.businesscentral.dynamics.com/v1.0/{{tenant}}/{{environment}}/api/{{publisher}}/{{apiGroup}}/v1.0/companies({{company}})/salesReturnOrder?$expand=items
in your docker url you are using the API endpoint, in your BC online url you are using the ODataV4 endpoint (this endpoint does not support deep inserts)
try changing
https://api.businesscentral.dynamics.com/v1.0/{{tenant}}/{{environment}}/ODataV4/Company('{{company2}}')/salesReturnOrder?$expand=items
to
https://api.businesscentral.dynamics.com/v1.0/{{tenant}}/{{environment}}/api/{{publisher}}/{{apiGroup}}/v1.0/companies({{company}})/salesReturnOrder?$expand=items
foo_bar
1
Re: Testcodeunits: Strange behavior when executing an action through invoke
Good morning,
I'm also not sure, why you get this error message.
But I would try to change the code like that:
I'm also not sure, why you get this error message.
But I would try to change the code like that:
SalesOrder.Release.Invoke(); SalesOrder.Post.Invoke();And see if there is a difference.
MortenM
5
Re: Inserting records in a page build from a temp table.
Hello!
If you want insert record in table you need create some code like this:
Rec - temp record
newRec - normal record
In your case Button "New" create new record in temp table
If you want insert record in table you need create some code like this:
newRec.INIT; newRec := Rec; newRec.INSERT;
Rec - temp record
newRec - normal record
In your case Button "New" create new record in temp table
Re: Use variables in flowfield calcformula
Hello!
In this case you cannot use 'if' in flowfield.
You can use some code for update Description filed in OnValidate trigger field 1 and field 2
In this case you cannot use 'if' in flowfield.
You can use some code for update Description filed in OnValidate trigger field 1 and field 2
Re: Use variables in flowfield calcformula
It's the way to go about this sort of problems, however the Description field becomes static and won't be updated if Customer, or Vendor or Item name changes, unlike in a 'normal' flowfield case.
If you need the Description to be updated you'd have to create a code, 3 separate functions subscribing to OnAfterModify in Customer, Vendor and Item and keep your Description field updated when the name changes in any of these.
As an alternative (albeit also far from perfect) you could create 3 'regular' flow fields, one for Customer, one for Vendor and one for Item respectively and control their visibility on pages.
If you need the Description to be updated you'd have to create a code, 3 separate functions subscribing to OnAfterModify in Customer, Vendor and Item and keep your Description field updated when the name changes in any of these.
As an alternative (albeit also far from perfect) you could create 3 'regular' flow fields, one for Customer, one for Vendor and one for Item respectively and control their visibility on pages.
Re: Purchase VAT Account Change for Purchase Line
So if you'd have the same product listed twice, on a purchase order with two lines, you'd want to have VAT posted to 2 different G/L accounts?
What is the purpose of such posting? What are you trying to achieve?
What is the purpose of such posting? What are you trying to achieve?
Re: Modern Lifecycle Policy implications
The Modern Lifecycle Policy is based on the previous lifecycle, but has drastically limited the time periods.
The former Mainstream Support was reduced to the first 6 months, the former Extended Support to 12 months.
As in the past, the first period (6 months) will also include extended features, while the following 12 months will only be used to implement bug fixes or legal requirements.
There will be no support after 18 months. At that time, however, 2 new major releases already exist, the third one is in the starting blocks, so this can be neglected. Who still customizes the base application will probably have more difficulties with the new cycle.
The goal: Update timely.
The former Mainstream Support was reduced to the first 6 months, the former Extended Support to 12 months.
As in the past, the first period (6 months) will also include extended features, while the following 12 months will only be used to implement bug fixes or legal requirements.
There will be no support after 18 months. At that time, however, 2 new major releases already exist, the third one is in the starting blocks, so this can be neglected. Who still customizes the base application will probably have more difficulties with the new cycle.
The goal: Update timely.
SilverX
5