InfoPath Dev

Senario as below,

In the back-end database there are three tables associated with this question:

1.        The table [Promotions] (which has a primary key on the field [Promotion_ID])

…this table links by the field [Promotion_ID] to the table…

2.        The table [Promotions_Price_Plans_and_Services] (which has a PK on the fields [Promotion_ID] and [Plan_ID])

…this table links by the field [Plan_ID] to the table…

3.        The table [Price_Plans_and_Services] (which has a PK [Plan_ID]) on the field)

The table [Promotions_Price_Plans_and_Services] has a primary key on [Promotion_ID] and [Plan_ID], so if a record is added to that table both fields are required.  That makes sense.  However, on the form I don’t want the user to have to enter the value, but because that field is part of the primary key, InfoPath insists on making it a required field.

If I try to edit the field in InfoPath to make the field not required the options are disabled – it looks like it’s taking its cue from SQL Server on how to set up that field.

How can I handle this?

Hello,

What values you want to set that field you can set using Rules or code. There is not problem to add the validation is that field is required but you have to check that field is filled with data or not while submitting the form.

Thanks for your quick response.

Could you be more specific for setting the field using rules or code.

Appreciate that.