Smartlist from Favourites: Users can now create a Smartlist from a favourite, retaining the search conditions and columns list. Great time saver.
Word Templates for Batch Approval Workflow: How about the ability to view the entire batch content before approving? That’s exactly what this feature is about. Excellent feature. This would further eliminate GP application dependency for trivial tasks.
I am particularly excited about the last two in the above list; AA Access and Smartlist Designer Export/Import.
The gap between Smartlist Designer and Smartlist Builder is slowly (yet steadily) getting filled. While Smartlist Builder is one of its kind, Smartlist Designer now gives customers a lean version of Smartlist Builder that would satisfy most of the requirements. I am happy as a consultant that I now have an improved Smartlist Designer to talk about with customers/prospects.
Mark highlights the Smartlist Left Pane curse (what else do you say if you see half of your screen is occupied by the Smartlist Favorites tree view and only half being allotted for results?) and a suggestion that was made by Sivakumar V.
Most of the queries that I am receiving from my users regarding Smartlist is like below:
1. Why my Smartlist Favorite is being shown to all? 2. I created a Smartlist Favorite in one company. It is not showing up in other company. Why?
Answer is quite simple and straightforward. They had not selected an appropriate *Visible To* option.
Smartlist favorites can be created with either one of available four different visibility options.
1. System 2. Company 3. User Class 4. User ID
Shown below is how it looks like:
1. System: Visible to all users across all companies. 2. Company: Visible to all users, but visible only on that particular company. 3. User Class: Visible to all users under the user class in which the user who creates this favorite is, but visible across all companies. 4. User ID: Visible only to this user, but across all companies.
Warning: Method shared in this post is NOT supported or advised by Microsoft team. This article explains a SQL method and therefore the intended audience is a GP and SQL Consultant / Developer / Administrator.
Couple of Smartlist Favorites created by an end user, but created it with a wrong visibility: Visible by User ID. What this user should have selected is: Visible by System. Since these favorites are suppose to be accessed by all Users across all Companies.
This end user is currently out and even as SA I could not access the Smartlist Favorites. Easiest and direct approach is to reset this user’s password, modify the smartlist favorite and notify him of the new password. Once this user is back, he/she would change the password.
But, is there any other simplest method for someone like me? A GP & SQL Administrator? Of course, I do.
I can modify a Smartlist Favorite using a simple SQL UPDATE statement, targeting the Smartlist Favorite tables ASIEXP81 and ASIEXP86. Display Name for these tables are Smartlist Favorite Master and Smartlist Favorite Columns Master respectively. Both tables are in DYNAMICS database.
Below are SQL statements that I used to change the visibility:
UPDATE DYNAMICS..ASIEXP81 SET ASI_Favorite_Save_Level = 1, USERID = ”, CMPANYID = 0 WHERE ASI_Favorite_Name = [Favorite_Name_Given_By_That_End_User]
UPDATE DYNAMICS..ASIEXP86 SET ASI_Favorite_Save_Level = 1, USERID = ”, CMPANYID = 0 WHERE ASI_Favorite_Name = [Favorite_Name_Given_By_That_End_User]
In above statements, field ASI_Favorite_Save_Level is the VisibilityType that we set up when we create a Smartlist. Value 1 denotes the first option in that Drop Down, which is SYSTEM. Since I have to set visibility to all users across all companies, all I have to do is to set USERID as an Empty String and Company ID as ZERO.
This will change a particular Smartlist Favorite’s visibility as required.