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

Question

Question

Populate address block from SQL table

asked on August 14, 2017

I want to populate an address block from a SQL table but when I go to do the lookup rules I can’t see the address block variable listed as an option to fill and there are no settings on the address block on the form layout.  Thoughts? 

0 0

Answer

SELECTED ANSWER
replied on August 14, 2017

Hi Michelle,

Lookup rule does not supported match/fill address field in current version. We got feature request for that but it's not implemented yet.

You could use single line field to store address values separately and use lookup rules to fill those fields.

1 0
replied on August 15, 2017

I thought that might be the case, but wanted to make sure, many thanks for the response!

0 0
replied on August 15, 2017

Michelle, I am sending you an email with two options as a work around.

1 0
replied on March 4, 2019

Hello,

I have the same issue.  Is it possible to send me the information in the e-mail noted above in order to populate an address?

0 0
replied on March 7, 2019

Rolayne, I just happened to still have that email! I've copied the content below since the exchange included other discussions not relevant to the address block question.  I ended up using separate fields, but did not use the CSS to make up the block.

 

From John Evans:

 

No default way to do this yet in the current version of Forms, I assume you found this out on Answers. You would be able to use JavaScript to do or create separate fields for the address and write your own CSS to make a block out of the fields.

 

The real issue is that Laserfiche treats the current block as a single entity not 6 separate fields. So, you create 6 and fill each one, or one and fill it with a series of data returns with commas.

0 0
replied on March 7, 2019

Michelle,

Thank you for sharing, I appreciate it.

0 0

Replies

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

Sign in to reply to this post.