Tech Tuesday: Using Built In Gotos with SmartList Builder
Tuesday, September 15, 2015With the first version of SmartList Builder from eOne Solutions for GP2013 was released, we added a new Goto type called Built in Gotos. This new Goto type replaced Advanced Gotos which were used on previous versions of Microsoft Dynamics GP. A Built in Goto will allow you to use any of the Gotos that exist on any of the default Microsoft Dynamics GP SmartLists on a custom list built with SmartList Builder. This will allow you to populate windows such as Payables Transaction Inquiry, Purchase Order Inquiry, Receivables Transaction Inquiry and Sales Inquiry which cannot be opened directly using the Open Form Goto type as the fields are locked on these windows.
In addition to these four inquiry windows there are many other default Gotos that you can easily apply to your custom SmartLists using the Built in Gotos. To setup a built in Goto you need to supply a Description, choose a default SmartList and default Goto and assign the proper parameters from your source table. The examples below show how to setup the Built in Gotos on a custom SmartList to work as Advanced Gotos did on previous versions of GP.
Using the default View goto from Payables Transactions
Using the default View goto from Purchase Orders
Using the default View goto from Receivables Transactions
Using the default View goto from Sales Transactions
Questions? Feel free to leave a comment below. Thanks for tuning into our weekly Tech Tuesday!
We have upgraded a customer to GP 2015 and have installed the update to smartlist builder. The new gotos work very well but I cannot remove the old “Advanced Go Tos'” because that product doesn’t exist, so they cant be deleted from the list.
I don’t want to have to recreate the smartlists from scratch because they have all kinds of calculated fields and gotos.
What are the tables I need to access in order to remove the old gotos , so they don’t appear in the list?
Thanks
These gotos are in the SLB10400 table in the DYNAMICS database. You can remove them by running the following:
delete DYNAMICS..SLB10400 where SmartList_ID = ‘Enter Your SmartList ID’ and GoTo_Number = Enter the GoTo_Number you need to remove
I have created a Smartlist that uses a SQL view and I am trying to create a GoTo for the Sales Transaction Entry window or Sales Transaction Inquiry window. I have tried everything possible and nothing seems to work. Does list functionality work for Smartlists created from SQL views.
Hi Jared,
Same case as Chad.. How can you link a SQL view value with an Inquiry form (i.e. Saled Document Inquiry) to allow for end-users to view the data.. GoTo throws an error when you try this, stating the field is locked (which is true in an Inquiry form)..
Beat & Chad,
I don’t see where the source data coming from makes any difference. But assuming it does (perhaps your View returns “Invoice” instead of 3 for the SOP Type for example) then you’d need a calculated field to change the words to an integer and then you map the calculation instead.
As for the “GoTo throws an error when you try this stating the field is locked” – that means that you are creating your own GoTo using the “open form” method and setting fields.
The purpose of these above Built-In GoTo’s is so that you DON’T have to create your own and can just pass the necessary params and it’ll open & correctly populate the window for you.
I have a smartlsit that shows every invoice and credit applied to a check. the go to should go to the view of each transactions listed. however,, they all point to the same one. any ideas?
Nice article.
I wanted to add something I learned, maybe it will help others.
I created a Custom Aging report and provided a GoTo for it to open the Receivable Transaction in the proper window (based on Document Type.) My smartlist was based on a View. When I added the table it had asked for the Key Fields. This is important to get right or the GoTo will not work properly. My initial setup was set to CustomerNumber as the Key. When I used the GoTo, it would open the Inquiry window but with the wrong Document. (It also did not open anything other than the Receivables Trx Inq Zoom window.) I updated my Key to include CustomerNumber, DocumentNumber and RMDTYPAL. This then resolved the issue with the GoTo. It now opens the correct Inquiry window and for the right document number.
Hope this can help others.
-Pat
Great point, Pat! I had not included as a key field and experienced the same issue . Thanks for posting.
Jennifer
If there is a third party like Wennsoft Job Cost, where there is no built-in, is there a way to trigger “clearing” a field on a window before running the field script on the “Open Form” go to?
Jen –
there isn’t a “clear field” method on the goto. but you could make a calculation to return an empty string.
then in the goto, just use the “set field and run script” and set it to the calculation which is empty (empty string or 0 or whatever the field needs).
I built a smart list with account number, I would like to double click on the account and have it go to the account transaction smart list and pass the account number as a filter? Can we do that?
These 4 examples are just showing the replacement for the Advanced GoTo functionality.
All of the existing GP smartlists that have GoTo’s everywhere should all be duplicated in the Built-In Goto functionality with SLB. Just look in the smartlist that would have this functionality (Accounts in this case) and choose the same GoTo name that you would see in normal GP Accounts and it should work the same way (View in this case).