Auto-populate a lookup value based on another lookup field does not work - InfoPath Dev
in

InfoPath Dev

Auto-populate a lookup value based on another lookup field does not work

Last post 01-08-2014 11:53 PM by donstephen. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 01-08-2014 06:10 AM

    Auto-populate a lookup value based on another lookup field does not work

    Here is the (simplified) scenario which caused me a problem :

    List 1 - "Customers" has

      "Customer"

      "Address"

    List 2 - Orders has

      "Order #'",

       "oCustomer_lookup" - a lookup field based on the "Customers" list 

       "oAddress" - a text field which I intend to auto-populate from "Address" in "Customers"

       "oCustomer_txt - a text field which i inserted just to demonstrate a point (see below)

    Here is the problem:

    In InfoPath form for "Orders" I create the data connection to "Customers", and set a "change field" rule for "oCustomer_lookup" with the filter, intending to update "oAddress",  but "oAddress" does NOT get populated.

    Now I am doing the same for "oCustomer_txt" which I type manually (it is the same result if I use  a choice field) and it WORKS like a charm.

    What works fine with a text or choice field as a trigger, does NOT work with a lookup field...

    A word of widom, anybody?

  • 01-08-2014 08:26 PM In reply to

    Re: Auto-populate a lookup value based on another lookup field does not work

    Hi york31,

    I'm not sure yet how your form is set up, but are you pertaining to a person/group picker (people control)?, if not may I have a sample of the filter value for the lookup field? Since you were able to query using a different field, then the only problem I'm thinking of is the filter query value you are using. 

    Don Stephen Lambatin / Support Engineer
    Qdabra Software
  • 01-08-2014 11:41 PM In reply to

    Re: Auto-populate a lookup value based on another lookup field does not work

    Thx for the fast response.

    I am not sure how I can send you a sample, but here is a simplified example that can be created in 5 minutes.

    1. Create a list named "Projects" with 2 fields, both of type "Single line of text": 
      •  "Title",
      • "Project_no"
    2. Populate it with two entries:
      • {"Project A", "111"},
      • {"Project B", "222"}
    3. Create a list named "Orders" with 3 fileds:
      • "Project Title" (single line of text),
      • "No_txt" (single line of text),
      • "No_lookup" (lookup of "Project_no" in the already created "Projects" list)
    4. Create an InfoPath form for "Orders"
    5. Try to populate"Project Title" with "Title" from the "Projects" list, whenever "No_txt" changes (e.g. type "111" manually) - it works!
    6. Try the same for a change in No_lookup" - it does not work for me.

    YK

  • 01-08-2014 11:52 PM In reply to

    Re: Auto-populate a lookup value based on another lookup field does not work

    Thank you for the additional information. It seems that No_lookup is not returning the correct value. May I know what type of InfoPath control the No_lookup field is? If this is a drop-down control, you may want to check the Value and the Display name by right clicking the field's properties, and replace the Value with the corresponding value to the Projects list.

    Don Stephen Lambatin / Support Engineer
    Qdabra Software
  • 01-08-2014 11:53 PM In reply to

    Re: Auto-populate a lookup value based on another lookup field does not work

    Thank you for the additional information. It seems that No_lookup is not returning the correct value. May I know what type of InfoPath control the No_lookup field is? If this is a drop-down control, you may want to check the Value and the Display name by right clicking the field's properties.

    Don Stephen Lambatin / Support Engineer
    Qdabra Software
  • 01-09-2014 01:04 AM In reply to

    Re: Auto-populate a lookup value based on another lookup field does not work

    This solves it.

    Thanks!

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