[JCirocco Contributions: 0Level 1☆]

I have 2 different item searches that references a custom item field for SCA which holds Web Store Features. When I include this custom field in Saved Searches I see the results are always truncated with the (More…) BUT when I export to CSV, one of my searches exports the full field and the other exports the exact same field truncated with the More… as the end of the field.

At first I thought it was the amount of data exported so on the search with the truncated CSV results I narrowed down the number of records and columns such that the resulting file is less than half that of the one that works. Still broke.

I then noticed on the truncated CSV version that the custom field was the last field so I moved it to be placed in the same order as the search that works. Still truncated.

Has anyone ever come across this before or can shed some light on how we can reliably export the full field?

Thanks in advance.

John
This is a cached copy. Click here to see the original post.

[al3xicon Contributions: 0Level 1☆]

Just a quick thought – instead of the field itself, what if you place it inside a Formula (Text) column, does it still truncate it then?

[JCirocco Contributions: 0Level 1☆]

Alex, Good thought but the only thing it does is truncate BUT removed the More…

[david.smith Contributions: 0Level 1☆]

Let me know if you need this scripted John.

[Dew Contributions: 0Level 1☆]

We had this issue with the standard field “Detailed Description”, perhaps your issue is the same. After a lot of back-and-forth with support I got this response:

Unfortunately, due to the limitations imposed by underlying technology (Oracle) we are not able to display in certain cases Detailed Descriptions longer than 1300 bytes. These cases are rather rare and are caused by a combination of certain feature set in the customer account and criteria used in the search. Therefore, we recommend changing the search criteria to avoid the truncation happening. This limitation will be documented in the online help.

This was defect 365415, never resolved. They did update the documentation for “Setting Up Items for the Web Site” to say that you can only enter 1300 characters for the Detailed Description field. You can actually enter more, but you just might encounter this problem.

[JCirocco Contributions: 0Level 1☆]

We got our response yesterday that if we use Inventory Location in either the criteria or filters, that particular field will be truncated. I made a copy and removed Inventory Location from the criteria and it was not truncated. Our problem is that this is an export used to push inventory availability to other store fronts and we only want the available quantity for a specific location. We are going to see if scripting will cause the same results.

[al3xicon Contributions: 0Level 1☆]

What if instead of inventory location as such, you used something like {inventorylocation.internalid} ? Sometimes I find that “fooling” NS by using an ID instead of a list/record will achieve the desired result.

[JCirocco Contributions: 0Level 1☆]

Alex, Thought there was a glimmer of hope there but it also truncated. Thanks for the idea though

---

al3xicon replied on 08/23/2016, 08:20 AM: …damn it.

[JCirocco Contributions: 0Level 1☆]

Also just tried the Bin join and that didn’t work also.

[Author]

Posts