Wednesday, 31 January 2018

Add new Value to Combo-Box via Automation Steps

Hi All,

Lets assume that you need to add a new value to combo-box control without any dependent logic. And you do not want to do this with Customization as you do not know that. And with Acumatica it is really easy to do.

Lets check an example where you need to add new source for leads. "Source" is just for informational purpose and does not have depended logic (in other words there is no different business logic depend on selected value). So that means that if we add a new value there we do not break anything.
If your combo-box has logic associated (fields enabled disabled / different calculations) than you may need to consider code customization instead of approach described here.
Acumatica Leads

Ok, so if the above conditions is met, we can proceed with adding values thought Automation Steps. "Automation Steps" is automation configuration in Acumatica that allows you to dynamically disable enable controls, add buttons, combo-box values depend on "step" where your document is currently in. For example if document is open you can print report, but if it is closed you cannot.

Here with Automation Steps we can add non-programmatic customization for some fields. Lets add source field for step Open. For our task step is not important as you can add value on any step, but for other tasks you may need to add fields/buttons on every step where you want to use it.
Acumatica Automation Steps

 Than you can use "Combo-Box Values" button to see and add there your own values.
Acumatica Automation Steps with ComboBox

As soon as you save the step you can refresh Leads screen and find a new value there.
Acumatica Leads with Custom Source

Hope it helps and have an easy configuration!

Tuesday, 16 January 2018

Show/Hide Grids on the Fly

Hi Everyone,

Sometimes you need to show user interface differently depend on parameters selected. Here I want to show you an approach where you can show different grids depend on parameters selected in filter.

You may need different grids in the following cases:
  • If have different data access classes (tables) to show.
  • If you need to have different grids layout depend on parameters.
  • If you  need to to have different columns configurations.

Friday, 12 January 2018

Multi-Select Selector

Hi There,

Want to share with you hidden way to add a multi-select Selector control to have better filters.
Acumatica Multi Selector

There is a special UI Control px:PXMultiSelector that allows you to select multiple values in the same field. Values will be stored in the field with Semicolon Separator. For example in the field like shown above we will have following value: ACTUAL; BUDGET
Acumatica Multi Selector Value

To add such control you need to do following:
  1. Define a selector on the DAC field. Please note that you should disable Validate value, as selector will try to search combined value in DB and fails with error.
    1. [PXSelector(typeof(Ledger.ledgerCD), ValidateValue = false)]
  2. Second step will be UI control definition. Note that there is no such control in the list of available controls, so you have to edit ASPX directly, but it is easy to replace PXSelector with PXMultiSelector. Do not forget Commit changes if you need to filter by this field. 
    1. <px:PXMultiSelector runat="server" DataField="Ledger" ID="CstPXSelector4" CommitChanges="True" ></px:PXMultiSelector>
Multi-Value selector will be good with new In<> Bql operator in Acumatica 2017 R2

Have a nice development!

Monday, 8 January 2018

Generate IN Receipt from the Code

Hi All,

In my experience I have quite a lot of questions like - how to create a document on the fly.
The answer is rather simple - we need to use the same objects as user interface and emulate user interface behavior.
  • As the main object that contains a business logic and validation is Grpah, we need to create it from the code and use for calling actions and pushing data.
    • INReceiptEntry graph = PXGraph.CreateInstance<INReceiptEntry>()
  • To create a new object we can use PXCache.
    • INRegister header = (INRegister)graph.CurrentDocument.Cache.CreateInstance();
  • Every container control form UI is linked with Data View that is linked with DACs and tables. As you may know from Acumatica Platform Achitecture UI sends just 4 commends to the server logic (Insert, Update, Delete, Select). So in our code we need to use corresponding data views and call appropriate commands with data provided.
    • header = graph.CurrentDocument.Insert(header);
  • Acumatica uses Events triggered from UI we need to emulate it with calling appropriate commands of Data Views when necessary. For example if you choose Inventory Item, Acumatica defaults some values. We need to emulate this call to server logic with Update command.
    • tran.InventoryID = 691; tran = graph.transactions.Update(tran);
  • We also need follow the flow how user creates a record. For example we need to fill document first before entering transactions.
So basically that is it.

Please check my simple example extension where I create a Inventory Receipt from button on Sales Orders screen.
Acumatica Create Receipt


Have nice development!

Friday, 5 January 2018

How to Translate Acumatica

Hi Everyone,

It is actually very easy to localize Acumatica to any other language. And here I want to go thought the localization process Step by Step.

System Locales
First thing we need to do is to setup a new Locale on System Locale Screen. Here you can specify name, type and some other preferences. Please note that locale should be active, you can login only to Active locales.
Acumatica System Locales
After you save, you will be able to see new locale on login page even if there is still no translation yet.
Acumatica Locale Selector
Please note that locales are different per each company, so to choose your locale you should select correct company first.

Please note that on the same screen you also can define your preferences for Numbers and Date Time representation with "Show Locale preferences". Also you can define in what languages should some Customers/Items and other descriptions be shown with "Setup Languages" button - this feature is called "Milti-Linguial Fields",

Collecting of String for Translation
Now we need to get strings for translation. But before that we need to collect them with Collect String Button. We need to collect strings every-time before translation as during version upgrades Acumatica may introduce some new labels, also during customization or report building you can add some new labels or error messages also. So the final set of string should be collected from exact instance right before translation.
Acumatica Collect Strings
When process has been you can extract Strings for translation from Acumatica.
There are 2 types of strings:
  • Bound Resources - Labels, UI Elements, Reports and some other things
  • Unbound Resources - Error Messages, TextBox Values, Time Zones, Mobile Sitemap and many others that are not related to particular screen in Acumatica.

Unfortunately Acumatica shows only bound or unbound in the same time, so you have to download files twice with "Show Only Unbound" checkbox defined and without it.

On the time when I made this article (in Acumatica 2017 R2) there were about 30000 strings with different length in each.

Do Translation
You can easily do translation of Acumatica labels in Excel or any other useful tool for you.
After translation has been completed you need to upload it back to Acumatica.
Acumatica Translation in Excel

Upload of Translation
In my experiments it is enough to upload data only for bound resource but I suggest you to upload translated file twice also for bound and unbound resources.

Done. Now you can re-login to Acumatica using new Locale and  you will see fully translated user interface.
Acumatica Thai Translation

Have a fast translation!

Tuesday, 2 January 2018

Attach Files with Rest API

Hi All,

In Addition to my topic with Acumatica REST API where I showed how to retrieve and save records using Acumatica Contract Base Rest API I want to share with you now how can you attach files with the same way.

To Attach file you just need to put binary data by following URL: https://<server>/entity/<endpoint>/<version>/<entity>/<key1>/<key2>/files/<filename>

For example, to attach file to stock item you will have following URL:

Acumatica Files Rest API

File will be attached to entity automatically.

Have a nice integration!