I’ve encountered a situation where I was modifying the Financial>>Account Transactions SmartList in SLB and somewhere in the process I lost several (System) Favorites. I have a backup on my test server and am able to query ASIEXP81 and see the old favorites. However, the difference is that it seems I reverted back to the out of the box SL (ASI_Favorite_Dict_ID = 0), whereas the favorites that were lost look to be tied to the SLB dictionary (ASI_Favorite_Dict_ID = 3830).
Results in production for Out of the Box favorites.
SELECT * FROM ASIEXP81
where ASI_Favorite_Type = 12
AND ASI_Favorite_Save_Level = 1
AND ASI_Favorite_Dict_ID = 0
ORDER BY ASI_Favorite_Name
Results on test server with SLB favorites (data does not exist on production server)
SELECT * FROM ASIEXP81
where ASI_Favorite_Type = 10057
AND ASI_Favorite_Save_Level = 1
AND ASI_Favorite_Dict_ID = 3830
ORDER BY ASI_Favorite_Name
If you look at the screen shot below, I’ve compared the SLB objects and as you can see my test server contains the modified version of the SL. However, I don’t see anything modified or added whatsoever.
I could use some help on how to get my SLB dictionary favorites back into production using the data I have from my test server. I think step one is to get the modified version back into production first. It doesn’t appear I can export the SL from TEST to import to LIVE. Can anyone provide advice on this? Thanks in advance!
*This post is locked for comments
Hello Jim,
I didn't see what version you're on for Dynamics GP? The reason I ask is, beginning with Dynamics GP 2013 R2, SmartList Builder ownership and support went back solely to eOne.
You can verify what version of SmartList Builder you're using, if running Dynamics GP 2013/R2, with this script:
Select * from DYNAMICS..DU000020 where PRODID = 3830
Microsoft's version of SLB would be a build of, or less than, 12.0.21
eOne's version of SLB would be a higher build of, or higher than 12.0.58
That being said, this information may potentially help you with this issue:
What happens is that when a user modifies a default SmartList in eOne’s SmartList Builder, it replaces the default SmartList with the modified version. The users that have SmartList Builder installed will only see the modified version since SLB hides the default. However, users that do not have SmartList Builder installed will see the default, since they won’t be able to see custom SmartLists build in SLB.
99.9% of the time I see this, people are modifying it by accident. The Modify button is not for making favorites, but people seem drawn to it like a moth to a flame. The Modify button opens either SmartList Desginer (if they don't own SmartList Builder) or it opens SmartList Builder. Most of the time what I see is people trying to create a favorite, hitting Modify, getting into SmartList Builder, they start clicking around thinking they are creating a favorite, get panicked, hit Save, and end up breaking the SmartList.
If you want to find out who modified it, you can run this query in SQL management studio against the DYNAMCIS database, for example:
select MDFUSRID,MODIFDT,* from SLB10000 where SmartList_Name='Account Transactions'
This happens so often one of our support guys wrote a blog article on how to disable the modify button using Modifier/VBA. There is even a package file in the article that you can download and import into the persons computer to prevent them from getting in there by accident.
There is also this link from eOne on how to remove modified default GP SmartLists:
www.eonesolutions.com/.../removing-modified-default-gp-smartlist
Thank you,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156