Keep up to date with the latest information about Microsfot Dynamics GP through articles from the Perfect Image and azurecurve blog.
SmartList Builder Will Be Disabled Until It Is Initialized By The System Administrator
August 19th, 2014 by Ian Grieve
I have been involved in several upgrade projects with clients recently where we have been upgrading them from Microsoft Dynamics GP 2010 through to Microsoft Dynamics GP 2013. Since this version was launched, SmartList Builder has been pushed back out to eOne, the original ISV.
So, after doing the normal upgrade process, we have then installed the latest version of SmartList Builder from the eOne website. However, this has not been a smooth process.
One of the clients started receiving the following error message whenever a user tried to access SmartList:
A quick read around showed that there was various steps which could be taken to investigate the problem. We also found an article on the eOne website itself (which now that I come to write this post, I can;t find to post the link) which guided you through the uninstall and reinstall process. However, if the initial upgrade didn’t work then we had little confidence that doing the upgrade again would work.
One step in the process outlined by eOne was some selects which allowed you to see if the table changes had been performed:
SELECT Extender_Type, Extender_ID FROM DYNAMICS..DDB10000 SELECT Extender_Type, Extender_ID FROM DYNAMICS..ERB10100 SELECT Extender_Type, Extender_ID FROM DYNAMICS..NLB10100 SELECT Extender_Type, Extender_ID FROM DYNAMICS..SLB10100 SELECT Extender_Type, Extender_ID FROM DYNAMICS..SLB10400 SELECT Blank_Field_CB FROM DYNAMICS..ERB11100 SELECT Blank_Field_CB FROM DYNAMICS..NLB11100 SELECT Blank_Field_CB FROM DYNAMICS..SLB11100
After running the above scrips, one column was found not to exist; Blank_Field_CB on ERB11100. The following script was produced to manually update the table with the missing column:
SET ANSI_NULLS OFF GO SET ANSI_PADDING OFF GO USE DYNAMICS GO ALTER TABLE ERB11100 ADD Blank_Field_CB TINYINT NOT NULL GO EXECUTE sp_bindefault N'dbo.GPS_INT', N'dbo.ERB11100.Blank_Field_CB' GO
Once this was done, users were able to log into SmartList without seeing the error.
As always, if you run a script against the GP database, ensure you have a good backup before starting.