Smartlist Builder Objects using SQL Tables and Views
Whenever we create a smartlist builder object using SQL tables and views, we need to be careful when exporting the same and importing it on to a test environment (or) the production environment.
There are a few things which you need to consider when u create a smartlist builder object using SQL server tables and views. When you export the smartlist builder object to an XML file, the database reference is exported as well, into a tag which looks like <NAME>’SQL Database Name’</NAME>. This will actually store the database which was referenced to create the smartlist object. So when this Smartlist object is imported into any other machine which contains a different database name, it would give permission errors, when the imported smartlist object, even though you have granted the necessary SQL permissions to the users. To avoid this, there are 2 options which you can follow.
1. If you are importing this to a single company installation, you can edit the above tag in the XML file and change the value to the appropriate database name of your environment.
2. If you are importing this into a multi-company installation, you can import the XML file and open the object in Smartlist Builder. Then go to Options and check the option called Multi-Company Smartlists and select the companies you need to include in the smartlist. This will fetch the data from all these companies into the smartlist. And at the SQL security for each user, grant the access to the appropriate company/companies to the users and they would be able to see the data from the appropriate company when they open smartlist. 
Till the next post, bye for now…
December 23, 2008
В· 
veeyeskay В· 
One Comment
Posted in: Dynamics, Great Plains, Smartlist Builder Total Views: 1,694
Pingback: How to use a SQL view in SmartList Builder « Victoria Yudin