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

Question

Question

Token Content Capturing Application Field Label Along with Field Content

Connector
Updated March 9, 2017
asked on June 3, 2016 • Show version history

Since a recent maintenance update has been applied to MS CRM Online, our Connector 10 profile to search for documents that are based on the SSN control is now not only returning the SSN number twice, but is also including the field label, SSN/TIN.  This is resulting in an error message.  Attached are a few snippets of the tokens that are being defined and the resulting content that is being returned, as well as the latest version of the updates that have been applied.

Any ideas on what could be causing this?

Connector 10 Profile to Search for MSCRM Online Contact Record Documents.docx (545.12 KB)
Download
0 0

Replies

replied on June 3, 2016

It seems like the contents of the page may have changed in structure. From your screenshots, it looks like you have already tried re-selecting the data, but if not, give that a try.

Have you tried using one of the other analysis options (where you currently have "JavaScript to find controls" selected)?

0 0
View 1 previous reply
replied on June 10, 2016

I have tried re-selecting the data and still get the same results.  Have not had success with other analysis options.  I tried a different profile that populates employee information from MS CRM Online to a LF Form (using Write Data action) and get a similar result.  Attached is a screenshot which reflects the field name from CRM being included in the data and the field data included twice, which is very similar to the other profile.

Any suggestions to resolve this issue would be greatly appreciated.  Thanks!

Connector 10 Profile to Populate Employee Information by Using Write Data.docx (357.54 KB)
Download
0 0
replied on June 14, 2016

Hi John,

 

Please open a support case. Please send the profile, tracing log and their corresponding xml file to support.

 

Enable tracing log can refer to https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/Connector/Content/Troubleshooting.htm%3FTocPath%3DConnector%7C_____11.

The log and their corresponding xml file can find the log location you configured.

 

Regards,

Qinmei

0 0
replied on June 15, 2016

A case has been opened with Laserfiche Support; we will update this thread as more information is available.

0 0
replied on March 9, 2017

A few months late...maybe a year late, but better late than never...

The issue was that the update to the application changed the id of the element in question to have a slash character which needed to be appropriately escaped for the JavaScript analysis of the application to not error out. In the original case at the time, we were able to update the profile manually to properly escape the character. SCR 146019 was filed for this and included in the recent release of Connector 10.2 so slash characters in JavaScript profiles should now be properly escaped if they come up.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...