Smartlist shows weird characters for Null values

(0) Share

Report

Posted on by Accounting Department

1,552

The Smartlist selection is Item Quantities and it uses the View slbItemQuantities and this is out-of-box view I believe. The tables in this view are IV00102 and IV00103 which is Vendor items.

When there is an Item that does not have a Vendor Item, or if no default Vendor Item, the Smartlist shows weird characters and cannot be exported to Excel.

I tried updating the view to use isnull(....) but that gave me an error in Smartlist.

The only way around this is for us to use a specific Site (Location Code) but in one case there was a Site that had weird char's where the Item had more than one site.

How can we fix this?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Bill Campbell 12 on at

Like (0)

Report

Good news for me and that is I am not the only one with this matter.

In our case the client had entered a comment on an Order and when printed on paper all is well, however, when generated to Smartlist a 'weird' character was inserted and then as above no export to Excel.

In our case the solution was to remove the column from the Smartlist that contained the 'weird' character and then the export worked.

Not likely the solution for the case noted above, but a thought might be to remove the column and see if that resolves for your case as well.

However the underlying question is why is Smartlist populating with 'weird' none exportable characters?

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

As you mention an slbItemQuantities view, it appears that you're using SmartList Builder?

I verified on my GP 2015, 2016, 2018 versions that Dynamics GP, by default, doesn't have any objects at all that begin with 'slb', so I imagine that is the case here.

I just mention it as I'm curious if you get the same behavior removing SmartList Builder from the equation? (You'll most likely need to use or install a 'clean' instance of Dynamics GP without SLB or any third-party products, as removing SLB from the Dynamics.set will cause an error to be thrown if you don't also remove all the addin files associated with it, when you attempt to launch the GP application).

Thanks

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi all,

I ran into a similar case recently with a customer being on GP 2016 and having SLB installed.. It appears that SLB is replacing the default out-of-the-box SmartLists that are built-in to GP by its own version... This can have some dramatic side-effects apparently, as I exported the code for both the slbItemQuantities and the Microsoft ItemQuantities views and compare the code.. they are very different, and though they more or less pull data from the same source tables, the approach is very different.

As a result, the ItemQuantites view would return valid data quite quickly in SmartList (after I created a custom SL using this default SQL view), whereas the built-in slbItemQuantities would never return any data and just "hang" GP forerver.. There would a task in the Process Monitor called "Retrieve Records.. " or something similar, followed by some ASI_ task (which indicates a SmartList query), but it would never complete.

The open Smartlist at the bottom would show a status "Exploring..." and never complete. After investigation with the customer, it turns out that the default SL used to work fine, but a recent increase in rows in the Item Location table (IV00102) would led to a large number (about 420k) of rows and my feeling is that the "slbItemQuantities" is to convoluted with its SQL joins that it cannot cop with the large amount of records in IV00102. The Item Master table only has about 2700 rows, but the customer has about 150 sites defined in the system.. Turns out someone recently discovered that there was an easy way to quickly assign ALL sites to every new Items, and this was causing the huge increase of rows in IV00102..

Nonetheless, this should not prevent the default view to return data, especially when it is limited to the first 1000 rows. We discovered that somewhat the default Item Quantities SL would work when using one of the favorites that had some filters applied.

My Question: is there a way we can replace the default views starting with "slbXXXX" that were created by SLB and get SL to use the built-in SQL views Microsoft provides with GP ?

I don't mind SLB adding their own views, but they should not replace the default built-in SL's for GP...

Was this reply helpful? Yes No
Accounting Department 1,552 on at

Like (1)

Report

Thank you for this. Totally agree with you on that last point!

We did find that many out-of-box Smartlists were replaced by slb.

Many of the user-created versions below the main Smartlist were created after. So if we replace the slb with out-of-box, all the users will lose their version. This is going to be a long process to get it all cleaned up, but plugging away as we have time.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (1)

Report

Thanks Barb,

I found this eOne blog post from a few years back that exactly describes the whole conundrum around SLB and the default out of the box SL's.

I've taken steps to disable the 'Modify' button thru SLB security so regular users wouldn't confuse the "Modify" button with the columns or filter button.

www.eonesolutions.com/.../

With this it was very easy to revert the default SL to the out-of-the-box version of GP..

Was this reply helpful? Yes No