Question

Chrome and Advanced Searches

Connector

Updated July 23, 2015

asked on July 14, 2015

Not sure if anyone out there has run into this – I have a client where Advanced searches are not working via Chrome with the LF Connector 9.01. Using the exact same advanced search on Connector via IE – when we setup for use with Chrome the searches do not return any results... If I place a specific value into the Advanced search it works, but a soon as I go back to %INPUT nothing is returned… Chrome is set to auto-update – testing with Laserfiche Forms 9.2.

Thanks - Brian

0 0

Answer

APPROVED ANSWER

replied on July 22, 2015

Can you test this in the newly released Laserfiche Connector 9.1? I wasn't able to recreate the issue using your original example of accessing Laserfiche Forms in Chrome (v44 in my case), performing a lookup on some value, then running a Laserfiche Connector profile based off of one of the returned values to search in Laserfiche.

0 0

Replies

replied on July 14, 2015

Hi Brian,

Is the issue that Connector isn't sending the query over correctly, or that it isn't parsed right in chrome? I assume you mean in Web Access 9.2 running in Chrome? If you paste that query into chrome as a URL, does it work? Can you provide an example query? Thanks!

0 0

replied on July 15, 2015

Hi Justin - thanks for the reply - here is what the client is attempting to do - has LF Forms open and has brought up information on an employee via their employee number - then using the employee number via the LF Connector we want it to go into Laserfiche client and return all items pertaining to said employee number via a field search - if we do this in IE it returns the correct results. If we setup the same Advanced Search via LF Connector and Chrome, it does not fail, but does not return any results. If in the Advanced Search criteria I call out a specific search term, such as "5593" then it will work. But if I use "%INPUT" no results. I'm working on getting a copy of the Advanced search from the client, but as a test, we tried several - all with the same result. I will try to post the query into Chrome as a URL and see what happens.

Thanks!

0 0

replied on July 15, 2015

Oh I see, I thought you meant searching through Web Access in either IE or Chrome, you're talking about the source for the value itself. Do you have two different Connector profiles (one for IE and one for Chrome?) and have you confirmed that Connector can actually read the value through Chrome? Chrome may require some configuration for Connector to be able to read the values. Check out https://www.laserfiche.com/support/webhelp/laserficheconnector/9.0/en-us/userguide/#UsingLaserficheConnectorWithAThirdPartyApplication.htm

0 0

replied on July 21, 2015

Hi Justin - we can configure the Connector - it just does not return any results via the Advanced Search - here is a sample search:

{[]:[EmployeeNumber]="%(EmpNo)"} & {LF:Name="*", Type="F"} & {LF:LOOKIN="FranklinCounty8\Human Resources"}

We do have two different Connector profiles - one for IE and one for Chrome.

Thanks - Brian

0 0

View 1 previous reply

replied on July 21, 2015

Brian,

Using the IE profile, go to the site and run LF Connector on that page. After the Client is opened and the search results are displayed, go into the search pane and view the advanced search syntax that was just used.

Next, open Chrome, go to the same page, and run the LF Connector profile you made for that. In the Client, when no search results are returned, go to the search pane and view the advanced search syntax that was just used.

Compare these two and verify that the %(EmpNo) token is getting resolved the same way from both profiles, i.e. that it ends up using the same value. If the search syntax shown in the Client for both are the same, then next check to make sure that the profile is configured to connect to the repository as the same user. Perhaps the profiles are configured to use different users to connect to the repository and the user in the Chrome profile doesn't have rights to the documents that should be returned in the searches.

0 0

replied on July 22, 2015

Client test this AM - trying MUNIS instead of LF Forms:

Create a new profile from MUNIS's vendor screen, extracting the vendor number and then querying the field vendor number and all documents with that vendor. IE worked, Chrome returned nothing. Here is the results from the LF search as Alexander suggested:

New Profile Created

Chrome:

{[]:[Vendor Number]="false"} & {LF:Name="*", Type="DB"}

{[]:[Vendor Number]="10639"} & {LF:Name="*", Type="DB"}

It seems like the value isn't passing through.

0 0

APPROVED ANSWER

replied on July 22, 2015

0 0

replied on July 23, 2015

Hi Alex - the upgrade to Connector 9.1 addressed the issues - we were able to return results with both Munis and LF Forms via Chrome.

Thanks - Brian

0 0

You are not allowed to follow up in this post.

Question

Question

Chrome and Advanced Searches

Answer

Replies

Sign in to reply to this post.