Intacct: Finding Field ID’s for Smart Rules, Smart Events, API, and imports!

Today’s post will be a short one: A cool trick to help you in writing Smart Rules, Smart Events, API, and even imports!

You’re probably already familiar with the Intacct Catalog (found under Platform or Customization Services). It’s where you usually go to find your merge fields when writing Smart Rules, Smart Events, and anything in this format: {!PROJECT.NAME!}. (The object is the part to the left of the period, while the field id is anything to the right of the period. We’ll give you a tip today on finding the ID to the right of the period).

Catalog

Now that you know where that is, I thought I’d share an easier tip (which changed my life) to help you find these field ID’s (since the catalog, while useful, is not too fun to play around in).

Whenever you are on a page in Intacct and you would like to know what the field’s ID is, you can right click and select “Inspect Element”.

Inspect Element

A small window will appear either in the bottom or right side of your screen and highlight the field for you. In that line you’ll see a part that says “id=_obj__PROJECTTYPE “. Anything to the right of the obj__ is your field id. Easy as that!

Inspect Element Open-1

Advertisements

Intacct: Smart Rules

Now that basic Smart Rules are a breeze, someone is bound to ask about a more complicated situation. So let’s test some Smart Rule limits.

What if you have a situation where you need a Smart Rule to do one thing on a certain action, but another on a different set of actions? Is that even possible? Well let me tell you, that it is! Here’s a cool case that came up recently.

The Question:

Can a Smart Rule be created which required the Document field to be filled out during Journal Entry only for a certain account (ex: account 1110)?

The Problem:

If it was a dimensional field requirement, that could be easily managed in the Chart of Accounts in the General Ledger, but since Document Number is not a dimension that won’t work. To require dimensions for certain fields that can be found here:

test2

What we’re going for here sounds like an “IF” Excel type of function, right? (If the Account No is 1110, then require the Document Number, if the Account No is anything else, then do nothing. If it was Excel you’d just write: =IF(A1=1110,”required”,”not required”)). Unlike a Smart Event, a Smart Rule isn’t a two step validation. Intacct gives you one box to write the condition under which the Smart Event will fire. So how exactly do you write a conditional Smart Rule? Well now that we know that’s what we’re looking for, let’s get on to writing the condition.

Continue reading

Intacct : Smart Rules

1

Financial reports are only as good as the integrity of the data they are based on.

Data integrity is vital. If data is incorrect, you risk basing huge financial decisions on incorrect information. The problem with achieving data integrity is that there are often a variety of people entering data (some more detail oriented than others). (Unfortunately, as much as my inner control freak would like to, there is no way to check each task a person does). Therefore, it’s hard to maintain the accuracy and consistency of the data. That’s when Intacct Smart Rules come in handy! They place real-time rules (warnings or errors) within the system, helping remove inevitable user mistakes without you having to check everything. (It’s as if the user has a little guardian angel sitting on their shoulder telling them when they forgot to enter some piece of information.)

In this example I will show you how to create a Smart Rule that prevents the user from continuing (creates an “Error”) if the Sales Rep field is left blank on a customer record. So let’s get started!

Continue reading