Skip to main content

Mental note to self: AIF changes -> Incremental CIL build.

After using a couple of hours trying to understand why my newly created AIF-service was not doing exactly was it was supposed to do, I found the solution.

My AIF service uses a new table to accept some value from an external system.
When a record is introduced into this table, a new ledger journal with a ledger journal line is created, and the voucher the line gets in the journal line, is updated onto my new table.

This to allow for making it possible to use customized code in an AIF service, without having to make changes to the table methods of the Generel ledger journal tables and without risking custmized code made in the Service classes being overwritten by a service wizard update of the service.

I had completed and activated my service, and was testing it.
Then I discovered that I had forgotten to call the code to create the ledger journal, on my new table's insert-method, therefor I got records in my table, but no ledger journal.

So I quickly inserted the call to the method, and tested again.
Still no general journal generated. :(

After pondering this I decided to deactivated the service and try to activate som logging, to see what was going on, and then reactivate it.

And voila, now I got my general ledger journals.
The activation of my service had of course built new CIL-code.

Conclusion:

REMEMBER to ALWAYS incrementally build CIL-code, when you change ANYTHING in AX, that is used in an AIF service.
Labels:

Comments

Post a Comment

Popular posts from this blog

Suppressing the infolog

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {     ...
Post a Comment
Read more

Indicating mandatory field in a dialog (RunBase) class.

A classical problem is indicating that a field is mandatory in a dialog, when the field is not bound to a datasource/field in a datasource. Normally fellow developers will tell you that, that is not possible. I found a way to do this. In your Runbase-based class you can implement the putToDialog-method e.g like this: protected void putToDialog() { super(); fieldMask.fieldControl().mandatory(true); } where fieldMask is a DialogField object in your dialog. This will make the field act like it was a mandatory field from a datasource in a form, showing a red-wavy line under the field, and requiring the field to have a value. Attention: Your class has to run on the client.If you set your class to run on the server, you get a run-time error, when the fieldMask.FieldControl()-call is made.
1 comment
Read more

Dynamics AX 2012 ValidTimeState tables and form changing view from current to all

Valid Time State tables are new i AX 2012 a gives the developer the possibility to easily create tables that hold e.g. current setup data for various purposes, and at the same time keeping a "history" of the changes of the data in the table. For more reading: http://msdn.microsoft.com/en-us/library/gg861781.aspx I was tasked with doing a setup table with rates for calculating Vendor Bonus and I chose to base this a valid time state table. The customer asked for a button on the form, where you maintain the vendor bonus calculation setup data, so you could toggle viewing "Current setup" or "All setup" records (changing the view from actual to all records and vice versa in the form). I found that you can not change the ValidTimeStateAutoQuery property on the form data source in a form at run-time. It simply does not change anything, so I came up with the following solution: A boolean class member in the classdeclation method of the form: boolean ...
Post a Comment
Read more