InfoPath Dev

So, now let's try copying everything in your current view into your new view, publish, try form in browser, do the controls work as anticipated in the new view?

Well I'll be dipped.

 That fixed MOST of the formatting problems.  There is still some wierd things going on.  I'll tinker with rules until it works, I guess.

 I never would have guessed that a view could have gotten corrupted.  Is that what happened?

 Thanks!

Yes, that would be my best guess.

And now you know my top-secret troubleshooting methods. I always start with a clean form, see if I can reproduce the issue I'm having. If I can't reproduce in a new form, I try a new view in my existing form. If my new view doesn't show the same symptoms, I copy things over to my new view and proceed from there.

I'm sure someone with a lot of patience, some deep XSL knowledge, and a big bunch of free time could have found and diagnosed whatever was causing the problem -- having none of those things, I like my method.

So here's another wierd thing that I can't get sorted out.

I have a repeating table to record the employee's expenses (with the add/delete rows disabled).  Once they click a "Save" button, the expense is set to a particular status, saved to SharePoint list, copied back into the main data source to the appropriate table (conditionally formatted to sort by status).  This all works. 

After an expense is saved, I have qrules delete the user input expense table, and insert a new, blank row.  That works fine, too.

In the user input table there is a option button that sets the attachment field to either a picture or file control.  This works (posts back) only the FIRST time data is entered.  After the main table (user input/expense) is deleted and re-inserted, these controls don't post back to the server anymore. 

I've done some testing, and have found .

one rule that prevents the postbacks . . .

I have static fields at the top of my form for name, job number, etc.  I have a repeating table (insert/delete disabled) for users to enter expense information.  They click a save button after each entry to save this info to SharePoint (and sets it to Saved status).  I have another repeating table to pull data back from Sharepoint, and display conditionally on status. 

My "Job Picker" drop down list has 7 rules applied to it -

-Delete expense table (qrules) - deletes the expense table whenever a job is selected.

- Insert blank row (qrules) - inserts a new, blank row of the expense table

- Propogate fields - propogates other fields, such as job location, start and end dates, etc.

- Delete Saved Purchases (qrules) - deletes the repeating table bound to the SharePoint list (showing saved or other expenses depending on status)

- Set Query Fields - Sets the SharePoint query fields to filter on Employee and Job Number

- Query List - Queries the Expense List on SharePoint. 

- Copy Table (qrules) - copies the SharePoint Table into my main data source.

In the Expense Table (user input), I have an option button to display either picture control or file attachment depending on what user picks.  This needs to ALWAYS post back.  I also have a checkbox to allow user to set a status to "Pending", and a rule will set that status when a user clicks save. 

Now, when a user picks a job that has no previous data saved for that job, the postbacks work fine.  If the user picks a job that HAS previously saved data, the postbacks STOP working.  If I disable the last rule (CopyTable), the postbacks work no matter what job is picked. 

Why the heck would this happen?  Why is this table being affected by CopyTable, which is bound to a completely different table? 

Another interesting thing -

The postbacks don't work when the form is initially opened either.  Not until a job is picked ( a job without previous data, of course ).  Hmmmmm. . . .

I find this confusing as well, simply because the data is separate from controls in InfoPath. Thus, there is no reason that deleting, adding, updating data would change something like how a control works (barring, of course, conditional formatting, etc).

This behavior only exists in the browser.  The client works as it should. 

Since your issue seems to be one of postbacks, it is expected it would work in client as anticipated....

So, not to belabor the basics, but you have mentioned before you have various tables connected to the same data showing on your form, and that they have conditional formatting on them... any chance you have these controls on your form more than once and they aren't all set to postback always?

Well, the other tables are all the same schema as my SP list, and they are only to display data.  The problem controls are not there.

The attachment option button is bound to "attachmentType" attribute under "Attachment" (another thing to note is that the qRulesLink is not being submitted to SP, either, but I was going to save that for later). 

Do I need to have all the attachment controls set to postback always?

The other control to set the status is completely independent of everything else, and does not exist anywhere else in the form. 

It's strange that this only occurs when CopyTable finds an existing entry for this job.  If CopyTable get's error "Cannot find row specified" (which means it doesn't exist, right?), then this does not happen. 

Also, they don't post back initially when the form is opened. 

I'm reaching for that fork again. 

CopyTable doesn't run when the form opens, does it?

Yet your controls don't post back initially.

Try a sample form, see what happens -- just create a simple sample with the same controls that are causing you troubles on open in this form. Publish it and see how it behaves in the browser.

If your qRules link isn't being submitted to ShP -- is it getting populated prior to your submit to SharePoint list being run? Is it mapped?

CopyTable does not run on form load.

I don't know that using a sample form is going to show me anything here, as there are so many variables involved in my form.  I had published the "Attachment Type" form that you sent me before, and it behaved normally. 

And yes, my SaveToSharePoint is mapped, because it works fine in the client. 

 

Would it matter what position I'm inserting the row on?  I'm using default (last).  That still wouldn't explain why they don't postback on form load. 

Ok, here's an interesting development.  I added the rule to delete my saved purchases table (the table that get's pulled in from SP) on form load.  Now the controls post back on load.  This has something to do with this other table.  Basically, if there is data in the saved purchases table, the controls in the new expense table don't want to post back. 

/thinking out loud. 

Another wierd thing . . .

I removed the conditional formatting from the tables that show the saved data from SharePoint (multiple tables bound to the the same table copied over from SharePoint), and the controls post back whether there is data there or not.  Which doesn't make sense, because the controls I'm concerned with are not in those tables. 

Is it OK to have multiple tables bound to the same repeating table with different formatting? 

Anyone have ANY idea what the hell this might be happening!!??!?!!?!