Question

Moving with the result of a query that got white space returns an error

Workflow

Updated February 11, 2014

asked on February 10, 2014

I always use a table in SQL to convert the month number in to number a letter for example 02 changes in to 02 February and use that query result to move documents and always work fine

Suddenly in LF 9.1 and WF 9.1 stop working and workflow now sends an error that tell “Invalid object name”

I think it’s relate to the space between the ## and the text of the month because if I remove that from the equation works fine.

Did you have a hotfix for this bug?

Extra info: This only happen using direct results from the query, if the info it’s already in a field or if use info from fields that got the white space works fine.

I don’t want to create an unnecessary hide field just to put the result and then use it.

0 0

Answer

SELECTED ANSWER

replied on February 11, 2014

We'll fix the issue in WF 9.1.1 (due for release in a week or so). I would, however, just change the query (to a Custom Query activity, if you're not using one already) to use the RTrim function on the value.

You could also use the column to nvarchar datatype so SQL won't automatically pad the values with trailing spaces.

0 0

Replies

replied on February 10, 2014

It sounds like your table is returning data with either leading or trailing spaces. You can use SQL functions to trim the trailing space or run the data through pattern matching to remove the space.

Side question, though. Do you start out with a date, extract the month and then call into SQL to convert the number into the digit+name format? Because WF can format dates directly into that format.

0 0

replied on February 10, 2014

The issue is that I want that space; I don’t like how 02February looks

But I get your idea I’m going to use Apply format to “MMM” and also Apply Function “To Tile Case” to try to solve the issue.

But at the end, you still got a bug in your new WF because this doesn’t happens in early versions

0 0

replied on February 10, 2014

I meant a trailing space, not the one in the middle. So something like '02 February '.

0 0

replied on February 10, 2014

Yes I got like between 5 or 10 spaces after 02 February because the SQL column with that data got the possibility maybe of 20 characters I don’t remember

But this is the same table I got using since LF 8 and never got that error

0 0

replied on February 10, 2014

I'm not disagreeing on the bug part. There were some structural changes made for WF 9.1 that may have caused it, we're looking into it.

0 0

replied on February 10, 2014

One last question to know if actually I’m going to be able to use WF to make the conversion

In my laptop the token editor shows for “MMMM “02 Febrero and also in my client server

But when I execute the WF session in my laptop the month creates as 02 Febrero and in my client server 02 February. What dictates the language? OS or other configuration?

0 0

replied on February 10, 2014

The service picks up the language and date/time format from the OS (and the user specified in the WF Server service login).

0 0

replied on February 10, 2014

My client OS server it’s in English and I need the "02 Febrero" so I still need the query to make it stable

Let me know when you found a solution please

Thanks & Regards,

0 0

replied on February 11, 2014

Great idea, the trim works perfect.

0 0

You are not allowed to follow up in this post.

Question

Question

Moving with the result of a query that got white space returns an error

Answer

Replies

Sign in to reply to this post.