Monday, August 3, 2020

Excel Based Reporting. Velixo vs GI

Hi Everyone,

Please note a bright example of how OData in Acumatica can be used by Excel based reports.
 
This demo also discusses a new Excel feature Dynamic Array, that is something worth to look at.

So, please take a look at Velixo, which is Excel based Acumatica tailored reporter (and not only).

They have recently added Single Sign On (SSO).

Have fun 



All the Best,
Sergey.

Saturday, July 25, 2020

Removing List as Entry Point feature for Newer Versions

Hi Everyone,

If your clients are not really fond of this "new feature", especially when you open a data entry screen menu item and all of a sudden user is getting 100,500 records into your screen, with all server burden overload attached. We have an option now.

There is a way to switch it off. 

Via user interface it has to be done One by One for all the data entry screens, as shown here:



Note the screen name, open it, then click CUSTOMIZATION -> EDIT GENERIC INQUIRY:


And once opened here is the option you need to amend:


There are two ways of doing it - complete removal of the entry list, then un-tick the option, save, done. OR you can leave entry list there but restrict the initial load to 50 records only. then amend Select Top to 50.

This will guarantee no strain to your server any more.

Now, for those who read it up to here, a bonus, here is a script that will do all this for all screens at once, it works for all implementations, as long as you have not modified the GI manually:

update GIDesign set selecttop = 50 where companyid = 1 and PrimaryScreenIDNew is not null



All the best,

Sergey.

Monday, June 1, 2020

Restricted Use of Control Accounts in Acumatica (2019R2 and up)

Hi Everyone,

Let me share recent Douglas Johnson video on Control Account feature in Acumatica:



Please be warned however, that even though this feature was introduced with option not to choose account as a control account.
It will always check on certain scenarios like Reversing a Bill, whether AP account is marked as control account or not.

It may cause issues if your customization are sensitive to warning messages.

So please take note. However in overall feature is a right one.

Thank you,
Sergey,

Wednesday, April 8, 2020

REST based WEB Service. Using the Note field Correctly.


Hi Everyone,


Here is a tutorial on how to set/update the note field for records.

Setting a note value
To set a note value by the contract-based REST API, do the following:
  1. Retrieve the record in question
    1. Set your contract-based REST API request with the following settings:
      • HTTP method: GET
      • URL: https://<entity>/Default/<endpoint version>/<endpoint name>/<record name>
      • No parameters for request
      • Headers:
        • Accept -> application/json
        • Content-Type -> application/json
    2. Send the request. The response contains 200 OK status. The body of the response includes the list of fields of the record in JSON format. The following is an example
    3. {
      "id":"e72ca73d-ffcf-4b96-a07b-54988f9cd632",
      "rowNumber":1,
      "note":"",
      "CountNbr":{
      "value":"FCN000021"
      },
      "Details":[...],
      "custom":{},
      "files":[]
      }
  2. Save the request
  3. Update the note field
    1. Set your contract-based REST API request with the following settings:
      • HTTP method: PUT
      • URL: https://<entity>/Default/<endpoint version>/<endpoint name>/<top-level record name>
      • No parameters for request
      • Headers:
        • Accept -> application/json
        • Content-Type -> application/json
      • Body of the request (where NOTECONTENT should be the note):
      • {
        "id":"e72ca73d-ffcf-4b96-a07b-54988f9cd632",
        "note":"NOTECONTENT",
        }
        OR
        {
        "CountNbr":{
        "value":"FCN000021"
        },
        "note":"NOTECONTENT",
        }
    2. Send the request. If the request is successful, the response contains the 200 OK status code and includes the list of updated records in JSON format. The following is an example
    3. {
      "id":"e72ca73d-ffcf-4b96-a07b-54988f9cd632",
      "rowNumber":1,
      "note":"NOTECONTENT",
      "CountNbr":{
      "value":"FCN000021"
      },
      "Details":[...],
      "custom":{},
      "files":[]
      }
Important information to remember

  • Make sure to always specify the note parameter to the note value, even when it is not being changed, as otherwise the note will be set to a empty string. This goes for all PUT requests