Smartlist error on export to excel and where is smartlist designer in 2016r2?

(0) Share

Report

Posted on by Community Member

This is a two part question.

1. Where is smartlist designer in 2016r2? I cannot find it. smartlists I can find but not the designer.

2. When we do a fixed asset smartlist that combines two tables (so I am told) it will not export to excel correctly. it gives the excel sheet error and asks to recover. Then the date is not correct on the excel sheet. I have taken all the columns out of the sheet except one and it still errors out. Doesn't matter which column I keep it will still error out. thoughts? ideas?

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Suggested answer

ShawnMD 1,456 User Group Leader on at

Like (0)

Report

#1:

To get to SmartList designer, open SmartLists and hit 'NEW' in the ribbon. This is the only way to get to the designer window.

#2:

What error do you get? Do other Smartlists export without errors? I've seen this happen when 'nulls' exist in data sets.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

1. well that sucks. how do you modify one that you created?

2. no error, per se, it tries to export but excel gives the error. the error log does not detail where the issue is located. Other 'default' smartlists seem to export fine. As mentioned I even went as far as removing all the column but 1 and it still gives the same issue.

Was this reply helpful? Yes No
Suggested answer

ShawnMD 1,456 User Group Leader on at

Like (0)

Report

#1: Click on the Smartlist that you created, and then choose 'modify' from the ribbon - it launches the designer with your previously created SL loaded and ready for you to modify.

2. Can you check to see if you have any 'null' values when looking at the dataset in SQL?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I can run the tsql in SSMS just fine, there does not appear to be any nulls. I can copy the data from the query in SQL and paste in to excel just fine.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Oh I even did a filter so it would only grab one item in the query and still same issue.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

Hi Aaron,

Could you post a screenshot of the error message you getting in Excel.. ? it might something totally unrelated.... Which version of Office is installed ? 32- or 64-bits ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

64 and 32 bit both.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

Thanks Aaron,

Usually it's not a good thing to mix-up Office setups like this.. The GP Client is only a 32-bits apps and as such works only with the 32-bits version of Office.. I'm on Ofice 2016Pro 32-bits and never had issues with Excel & GP.

As a side note, did you try to click on that XML hyperlink to see what exactly was repaired (or attempted) ? it might give you a hint on the data that is causing the issue.. I've seen weird characters in GP that would cause such strange behavior when trying to export to Excel. Sometimes those are 'invisible' and are not an issue to SQL, but Excel has a problem to handle them.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

what check the XML hyperlink to get more info? who would have thought? yeah it just says it repaired some cells but not which cells.

As I mentioned I have tried with BOTH 32 bit and 64 bit of office with the same results. Also above I stated that other smartlists are not having an issue. I suspect it may be data as well but I have filtered out the results to one column and one item in that column and have the same issue.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

Aaron,

Check out this thread, and in particular the solution posted by Jim on Page #2... I ran a few times into such issues in the past, and most of the time the problem was caused by a user that copy/pasted infos from a web page into GP, appending an invisible character into a field, which GP as per say has no issues with, but the export process from SL to Excel goes thru XML and that is the problem..

community.dynamics.com/.../336175

Was this reply helpful? Yes No