How to prepopulate field based on a manually entered value from a previous field? - InfoPath Dev
in

InfoPath Dev

How to prepopulate field based on a manually entered value from a previous field?

Last post 03-16-2009 07:42 AM by jim_r. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 03-16-2009 07:42 AM

    • jim_r
    • Not Ranked
    • Joined on 03-09-2009
    • Posts 6

    How to prepopulate field based on a manually entered value from a previous field?

    Hi all,

     I have a "Billing Address/Delivery Address" section in a form that I'm trying to replicate.  I'm working in InfoPath 07 but working in a template that is compatible with 2003.

     Here's what I want to do:

    After a user enters a delivery zip code and hits [Tab], display the question "Is the Delivery Address different from the Billing Address? Yes/No"

    If they select "Yes", a new section with the Delivery address displays, prepopulated with the information entered for the Billing Address.

     If they select "No", a new section with the Delivery address displays, but the user must manually enter the information.

     

    What I've tried so far:

    I created the question (called del_bill_question) in a separate section and set this "question section" to hide if the billing zip code field is blank (it works!)

    I created a "delivery_address" section, added fields, and set it to hide (conditional formatting) if "del_bill_question" is blank. (also works!)

    Tried to get the data to populate in the delivery address section's fields by using rules (these don't work yet):

    If "del_bill_question" is "2" (No) (ie, the addresses match), then set the delivery address street to the billing address street, repeat this same rule with the city, state, and zip fields. 

    If the question = 1 (Yes) (addresses don't match), then allow the user to enter new data in the delivery address fields.

     Any ideas?

    Thanks,

    Jim

Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.