You are viewing limited content. For full access, please sign in.

Question

Question

A Quirky and Subtle Cloud Lookup Issue

asked on November 4 Show version history

We had a situation where we needed to export docs added to an on prem system from January in an on prem system, upload them to the Cloud and file them back into their original location.  We did a date search and exported the search results listing as a csv file, with the document path included.  The names did not duplicate.

The idea was to upload the report to a table, then use the document name to look up the path, and then use WF to file it away.

That all seemed simple enough, except our lookups were not hitting. After too much time, we discovered the following:

 

Two spaces after the colon in the original, one space in the table! That's enough for you to get no hit.

Even though the csv was quote delimited, the import process seemed to remove the second space. This also happened whenever there were two consecutive spaces.

When things go wrong, you gotta get very granular in your debugging. We never expected this!

 

0 0

Replies

replied on November 4

There is a preserve whitespace option when importing to a lookup table. Did you try that option?

1 0
replied on November 5

I did not, thanks for the tip!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.