InfoPath Dev

I have an Infopath form that requires 3 signatures. "I'm NOT going to use Digital Signature."

Currently, I am keeping these fields in my sql table via Web
Service. When the infopath form is initially populated, via a dropdownlist (dropdownlist1),
my fields (dropdownlist2, dropdownlist3, dropdownlist4 for
my 3 signatures) are blank and disabled.

At this point, I would like this to be
enabled so that I can select the signature (which currently consist of a list of employees) and submit the form to which the Web Service and Database are updated.

If I understand you correctly, you want to be able to choose an employee from dropdownlist2-4 if and only if there is a selection in dropdownlist1. Otherwise you want them to be disabled.

If this is the case, then you need to set you conditional formatting for dropdownlist2-4 to disabled if dropdownlist1 is blank.

If you want further to make it so each signature can not be selected until the previous signature is selected, then you can make ddl2 conditional on ddl1, ddl3 on ddl2, ddl4 on ddl3. Make sense?

You will also probably want to clear the value selected in ddl2-4 when ddl1 changes.

Greg Collins [InfoPath MVP]

I think you're close but the key issue is ENABLE and not disable. When I select an item from DDL1 all the fields on the form populate except DDL2-DDL4. The reason why these do not populate is because my current information in SQL for DDL2-DDL4 is 0. The problem is that DD2-DD4 is DISABLED. Thus, I can't put any information in them. I see where you can disable something, but where can I enable it.

Note: If I go into SQL and change the 0 to a good ID for the DDL2 field, the field becomes enabled.

Thanks alot


Darryl

I field can become disabled for several reasons. I was referring to conditional formatting which allows you to disable a control. Enabling that control is simply a matter of the condition failing, and thus NOT disabling the control.

Another reason a control can get disabled is if the field it is supposed to be bound to does not exist -- such as an optional element. If it does not exist in the form XML, then the control can do nothing, so it becomes disabled.

It sounds like what's happening to you is the latter situation. Do you know if that is the case... that the element is never being created in the XML? You should be able to find out by saving your form to a .xml file and looking at it in a text editor.

Greg Collins [InfoPath MVP]

I'm not sure of how to Save it to XML, but I tried exporting it to Excel and the DDL2-DDL4 fields did NOT appear in the list. Thus, they probably won't get transfer. I'm not familiar with the "Optional Element" which sounds like what I'll need. How do you produce this "Optional Element"? Since these fields may or may not initially be filled.


Thanks again


Darryl

Saving to XML is nothing more than File | Save. Anyway, you found out that your fields did not exist... so this appears to be your problem.

To learn about Optional fields, please refer to the InfoPathDev.com Dev Nugget titled, "The Difference Between Optional and Not Required", which can be found here:

"http://www.infopathdev.com/nuggets/#The%20Difference%20Between%20Optional%20and%20Not%20Required

Greg Collins [InfoPath MVP]

I've checked out the article and I'm still researching the XSD file in my Web Service. Picture this, I have 3 drop downs DDL2-DDL4 that always appear on the form (visually required). Although, nothing has to be in the DDL2-DDL4 box (I'm not talking about the Dropdown results, these items display properly if a valid ID is entered into the database, but currently this ID is NULL), initially. The fields need to be enabled so that I can initially select something from the list of DDL2-DDL4.

As previously noted, the list themselves DDL2-DDL4 are populated, but nothing is selected. The value that I'm attempting to send it from the database is NULL. But, when I look in my results of running the Web Service by itself, the names and the values for the fields that I need.... the ID and the Name, are not present. They are present in the upper definition part (although this section has no bearing on what we're trying to accomplish). I also notice that one of my fields <add2 /> displays its placeholder although no value is in it, but my fields (the ID and the Name) don't display....

These fields are visually required, but no input is required, but I should have the capability of selecting something, but the DDL2-DDL4 boxes are disabled. The fields are not visually optional, but the input is optional.


I hope that I haven't confused you.


Thanks again Greg,


Darryl

I think I've resolved the problem, it apparantly doesn't like nulls. I'm attempting to change my Stored Procedure to pass 0 or '' and I'll let you know if I run into any other problems.


Thanks alot Greg. In particular for your promptness.



Darryl

It appears that the sql issue is resolved. Now, when I select an item from the DDL I get the error "this value cannot be modified"


Thanks


Darryl

I'm glad your main issue was fixed. Without more details I doubt I can help on the error message you are receiving.

Greg Collins [InfoPath MVP]

Basically in my DDL2-DDL4 I can now select the ListItem, but upon selecting it I receive the error "this value cannot be modified". What exactly does this error mean? I have other DDLs on the page that I am allowed to change and the error doesn't display. The value is an ID and the Name is a string (which is what actually display in DDL2-DDL4. It doesn't matter whether the initial value in DDL2-DDL4 is empty or populated, it will not allow me to change it.

When I use other DDLs (that already are displaying) and use the same properties -> Data Connection: -> Entries -> Value -> and Display Name as I use for the DDL2-DDL4, it WILL allow me to edit them.

Figured out the problem.... I had set my XSD file for DDL2-DDL4 properties -> ReadOnly to True. Just in case you run across this again. Thanks for all your help, Greg.


Darryl

Cool! Glad you got it worked out!

Greg Collins [InfoPath MVP]