Acumatica, MYOB Advanced, and CEGID allow users with a Customizer role in the system to add custom field to any screen. If you have custom transaction fields in your Journal Transactions screen, you can use GL Writeback to populate those fields.

mceclip0.png

An example of a custom transaction field on the Journal Transactions screen

To populate custom transaction fields using GL Writeback, follow the steps below.

First, unless you already know it, you need to look up the internal name of the custom field, which is required to write back to it from Velixo.

To do so, on the Journal Transactions screen, select Customization -> Inspect Element, and then click the grid column header. The internal field name will be located in the "Data Field" row of the resulting pop-up window:

mceclip5.png

Looking up the internal name of the custom field using the Customization menu

💡 If the Customization functionality isn't visible, ask your ERP administrator (or anyone who has the Customizer role) to perform the above step for you and provide you with the internal field name.

Back in Velixo, on the Journal Transaction template worksheet, locate the row containing the transaction column names, and add a new column with a name exactly matching the internal name of your custom field in Acumatica:

mceclip6.png

Adding a custom column to the GL Writeback template

Next, make sure that in the template header, the Import Custom Columns option is set to Yes (see the screenshot above).

Finally, fill out the transaction template and click GL Writeback -> Import Current Worksheet. The custom transaction field in Acumatica will be populated with the values that you specified in the respective template column:

mceclip7.png

The resulting Acumatica batch with the custom field populated by the GL Writeback feature

⚠ NOTE: There is no pre-validation for importing data from custom fields. Make sure that all data you enter for a custom field is correct.

Writing to Other Non-Custom Columns

Besides custom fields, GL Writeback supports populating any other writable transaction field that is not present among the default Journal Transaction template columns.

For example, if your Acumatica instance is customized so that Customer/Vendor or InventoryID column is writeable (they are read-only by default), you can use GL Writeback to populate those. For more information on customizing your ERP, please contact your partner or implementation consultant.

Did this answer your question?