-
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 ...
-
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 ...
-
This behavior only exists in the browser. The client works as it should.
-
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'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 ...
-
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 ...
-
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!
-
Gotcha. Did it. It works like it should. Now I'm REALLY confused. But I've put the fork away.
-
Are you saying just to copy the tables from the main view to the new view? I would need the static fields and the repeating table to call the data. Wouldn't everything just be the same?
-
Well, that works just fine. I don't know where to go with this now. It's strange that my problem form works great in the client, but not in the browser.