-
The only thing I could think of would be if CTRL1424 wasn't in your current view - I'm sure you've checked that 100 times though. Oh, I guess you could also get that error if that control isn't bound to the field you are using for the XPathNavigator. I mean, your code looks just like the sample on the MSDN page for the method.
-
Your syntax looks correct, and since it is working in IP 2007, I'd anticipate it is correct.
Like I said, my only recollection on issues with current in IP 2003 was the use of it in default values. If this were my form, I'd try setting rules on the AccountNumber field to set these other fields and remove the default values and see if it ...
-
I see - so the issue is going to partly be too many columns in some instances - and IP doesn't let us conditionally format columns (and you wouldn't want to entirely hide them, since you may or may not have data in the field).
I guess you could always use a single table row with all your fields, and conditionally format each field to ...
-
You can attach it to a reply under the Options tab - I'm not sure how much help I can be as I no longer have IP 2003 installed anywhere.
-
Okay - so it has been a long time since I've looked at this, so I am going by memory here (and we know what that can be like).
In IP 2003, if I recall correctly, we could use current() - but not in default values. So you had to use rules to set your field's value if the current() function was needed. I think that if you create an IP 2003 ...
-
Hi - if you are using the 4.0 trial, and if you are using browser forms, you may indeed run into some limitations for commands that rely on SharePoint web services. I believe you can't admin approve forms in Office 365, and have to use Sandbox only - is that correct? If so, any commands that require full trust won't be available to ...
-
Hi - when you say "list-attached" form, what do you mean? A SharePoint List form? If so, is it for an external list? Or a regular list? Regular list forms can't have code, so my assumption is qRules would not work in a SharePoint list form.
-
That's a tough one. You'd think if the issue was authentication, the error log would include that. Searching just on DB_E_ERRORSOCCURRED(0x80040E21), I see some results that indicate this may occur with Integrated Authentication - is that what your UDCX is using? I wonder if changing to SSO would help....
-
What is the CAML you are using? Is your submit set up to submit the entire Batch node as XML?
-
I think your original post may have insufficient information for anyone to really understand where the issue is. Where is the line of code you posted running? Do you have two forms or one? Is the issue in the forms or the workflow, or do you need help troublshooting that?