Displaying the Account Number Separator Character for SmartLists Created With SmartList Builder

This one was rescued from the Microsoft Dynamics GP community newsgroup and I have to admit, it's perhaps one of the darn best Dynamics GP tips I have seen in a while -- and trust me, I have been around that long. Transcript of the question (courtesy of Bob Cool) and the response (courtesy of Habib Salim) in the newsgroup is as follow:

Search Accounts window

Bob asks:

I'm trying to figure out how to define a SmartList using Builder so that when you search on the Account Number, you get the Value box that splits the account into its associated components.
For example, our account numbers consist of three segments. If I enter a search criteria for the account number in any one of the standard SmartLists, the Value box has three distinct pieces, each separated by a hyphen.

If I use the GL00101 table in Builder, I would have to create a calculated field, concatenating all 3 segments together - but that won't show up as the 3 separate fields with hyphens between them in the Value box - all I get is a blank box to enter a string value.
Bud Cool, Accounting System Manager
HDA, Inc. Hazelwood, MO
GP 9.0, SP2

Habib Responds:

Bud, Pre-built smartlists show these columns as having an "Account Number" data type. However SLB does not allow you to define a string as an account number type. However, you can achieve what you want. Add the account index. In the display definition (right arrow) select the "Account Index - show account number " option. SLB will translate the account index into an account number for you, and it will show you that separator char in the value box. This will work for any account index such as IV00101.IVIVINDXHS.

Habib Salim is a Microsoft MVP and a regular contributor to the Microsoft Dynamics GP community newsgroup.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC


Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

eConnect Integration Service for Microsoft Dynamics GP 2010

Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 3