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

Question

Posted to Government

Question

Feature Request: Two Part Field

asked on November 13, 2014

For Tax Notices - Would like to have a Two Part Field

I have scanned in all of 2014 tax notices and applied a template that includes the Roll # and Legal Land Description (LLD).  I have made the LLD field multi-value, but haven't for the Roll # field yet, even though some of the tax notices reflect numerous different properties on one notice.

Really, what would be ideal would be to have a field that could encompass a Roll # and LLD that were tied together.  Roll #801430; LLD NE-30-041-12-4 on one line, as they will always be tied together. 

Purpose?  If all you have is the LLD, you could search for "NE-30-041-12-4" and when you found it, see the Roll # that is tied to it; then, you could do another search for the Roll number to pull up any documents with that Roll # on it.  A piece of correspondence may mention the Roll # or the LLD, but not always both.

Thinking even further, since every LLD is tied to one Roll #, it would be awesome to have a reference table where if you entered a roll #, the LLD would auto populate and vice versa.

To clarify:  Multi-value settings on two individual fields doesn't really work, because there is no way to know which of the roll #'s are for which of the values in the LLD multi-value fields when the topic of a document includes more than one property. 

Thx, Connie

 

0 0

Replies

replied on November 13, 2014

Try having 3 fields: Roll #, LLD and then a third combined field. Have workflow combine Roll#+LLD as soon as both fields are populated. Do you have workflow?

0 0
replied on November 17, 2014

I do have WF.  I like your idea, I could use it for some things, however, in this case, how would WF know which of the Roll#'s match the LLD?  I couldn't guarantee that the staff will understand that they must enter all the roll#'s and then all the LLD's in exactly the same order so that they would tie together properly.  Oh, unless WF could double check against a spreadsheet that listed what LLD match to each roll #.  Then, if it found a conflict, it could just leave that one alone?

0 0
replied on November 17, 2014

You could  have WF query a database (or excel) to validate any of the data. You could also use a constraint on the field. If I were you I would try getting that far. Once I get my wheels turning, further answers fall into place. 

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

Sign in to reply to this post.