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

Question

Question

Lookup Rules not working after migrating to another computer

asked on November 26, 2015 Show version history

Hello,

I had made Forms for testing on test machine, I moved the Database & export of the forms to new server.

All Field Rules & scripts are working fine.

 

There were two databases used for lookup, I migrated both of them also.

One of them works without issues & the second is driving me crazy.

I have even tried to create a new database & import the table in new database, but still it isn't working.

I have the old system working & the rules are exactly the same, I have tried all possible things, but it doesn't work.

 

Can someone PLEASE help???

 

There are no errors in event logs or so?

 

Thanks,

S

0 0

Replies

replied on November 26, 2015
0 0
replied on November 27, 2015

I found out that this functionality is not supported in 9.2.1, if the first field is in table & the other is out of table.....

 

Can anyone in LF justify this? How come this is a step forward? & to my surprise it's also not in Forms 10???!!!

 

I had to roll uninstall 9.2.1 & go to 9.2.0....

 

Thanks

0 0
replied on November 30, 2015 Show version history

Hi there,

What you describe is not a functionality supported by Forms. It's a bug in old version. Can you let us know your specific use case? (what kind of form, what's the data collected in table, in the field outside table, screenshot is also helpful). And we can know whether the lookup functionality covers it.

0 0
replied on December 8, 2015 Show version history

I got your business process. It seems you use table to achieve a certain layout. The table only have one fixed row. In this case, I would suggest you use CSS and Javascript to achieve the field side by side look. http://answers.laserfiche.com/questions/61682/aligning-side-by-side-fields-CSS-help  So that you can use the Lookup Rules among fields successfully.

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

Sign in to reply to this post.