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

Question

Question

Possible SDK Bug. Could someone test for me? Searching and spaces in the document name.

asked on January 16, 2019 Show version history

Hi all,

I'm using SDK 10.0 on a 10.2 repository that started as a 7 (I think... mostly sure). At any rate, the import thing is that under a previous version of LF Client, users were able to create documents with trailing blanks in the name.

  • For example: "Hello World "

When I run try to sub-type a returned EntryInfo from a search, I get a very odd message:

  • "Invalid object name"

There's not much more than that.

To replicate, you'll have to add the trailing space to the docname in the TOC table, then restart the LF service.

Then run a search and try to set a new DocumentInfo object:

Using oSearchResultListing As SearchResultListing = oSearch.GetResultListing(oSearchListSettings) 
 For intX = 1 To oSearchResultListing.RowsCount 
'The following line will fail with "Invalid object name" 
 oDocumentInfo = oSearchResultListing.GetEntryInfo(intX) 

If you have a moment, could you try this?

The fix for the customer was to mass-update their toctable to remove trailing spaces. So am now just curious if anyone else has this issue.

-Ben

 

0 0

Answer

SELECTED ANSWER
replied on January 16, 2019

I can reproduce it with the latest version as well. Bug reference ID 151779.

0 0
replied on November 10, 2023

Hi Miruna,

With 10.4 of the .Net Framework API, I am still able to replicate this. The documents display fine in the LF Client (I forgot to check which version was being used.)

Is there a recommended way to code around this, or should all names be trimmed at the database end? 

0 0

Replies

replied on January 16, 2019

Thanks Miruna

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

Sign in to reply to this post.