InfoPath Dev

InfoPath 2010, I have a form which needs to display read only, not be able to be changed. I want it to display the "Title" field not "ID" field. If the field is a text box it displays the "ID" field which is an integer value, if I change it to a Drop-Down list Box it displays the "Title" field which is what I want to display, but the user can change which will not work with my requirements.

You can use a calculated value. Select the secondary data source that provides the values to a drop down (if you put a drop down on the form), select the title field, and then add a filter - the filter would be that the ID in the secondary data source is equal to the selected ID. Attach your form under Options to a reply if you need a hand, ok?

 The fields are on the "Query SRs" view, the fields are "PM Approval Status", "TM Approval Status" and "SM Approval Status". The requirement is to have them read only , but display the "title" field and not the "ID". Prefer to have a text box read only. If you can give me a hand on one, I should be able to change the others. Appreciate whatever help you can provide. Thank you in advance

Try this - the reason we use a calculated value instead of a text box is because the secondary data source with the Title is repeating, and we'd have to have a repeating section for our text box.... However, I formatted the PM approval status to LOOK like a read only text box. :)

The PM said we are good to just change to a drop-down list, the user can "Change" the field value but it does not stick. I was not able to view your template solution

You need to download the attached file, right click & select design to open in design mode.

Thanks, got it, worked. The form is working, but when I publish I am getting error notifications about those fields, but the form works as planned when we run it. I will see if I can get the errors out

What are the errors? I'm guessing this is because IP thinks the expression box is supposed to be repeating data. Post your latest template back and I can manually clean up the view file for you.

Hilary, yes that is the issue, attached template. The other 2 things remaining with the form. The PM pointed out that the fields are bound to the dataFields, which are read write, instead of the queryFields, read only (or are we wrong on this). The PM is saying their is a chance the user could change the values for the fields if the they are bound to the dataFields. I have the fields properties as read only. If I switch them to the queryFields, the form does not populate the fields. Any thoughts? Also the command button at the top going back to the "Step 1" view displays the selected record in the drop down. The PM noted this may be an issue allowing the user to change the fields if it has gone through the "Approval Process", I have tried a few things including working with the rules but not getting the results I want. Any thoughts. Any assistance is appreciated. Thank you in advance

Fixed up form attached. Query fields are used to query for data - so, you set the query fields to the values you want back from you list, execute the query and data is returned to the data fields. Changed data will only post back to the list if the form is submitted. You can control that - set controls to read only, or use calculated values to display data. Secondary data can't be changed - so if you have controls on the form bound to secondary data sources, and the user changes values - submitting only submits the main data. You probably need to add logic to the button to clear all fields if you are going to let the user go from the "query for existing" back to the "create new" view.... Or maybe set the ID query field back to blank and execute the query again? Does that clear the form?

Thanks, can you briefly explain what you did so I can avoid this in the future? Also, playing around with the buttons, for this form I was able to add a new button that that went to a new record and it switched to the other form with a new record, cleared fields, with no other rules, so this requirement is met as the PM wanted. Happy Memorial Day.

 

 So - I have a blog post here on the bug I manually fixed up: http://www.infopathdev.com/blogs/hilary/archive/2012/01/19/ipfs-design-checker-errors-amp-print-preview.aspx

It sounds harder than it is. Basically, this is an InfoPath browser form bug - expression boxes don't need to be bound, but InfoPath adds that binding sometimes when we create them.

Have a great weekend!