-
So, I'm actually kind of surprised that this is working - in my experience forms have to be published to open correctly. But since it does seem to work, I don't imagine you are doing any harm by it - do your existing XML then open with the new template? Or do you have to relink them?
-
Oh my gosh - just ran into this the other week!
From an MS Escalation Engineer:Problem: You have an InfoPath form bound to a database. If only Inserts are performed, this works fine, and if only Updates are performed, this works fine. But if an Update and an Insert are performed in the same batch, then the Update changes its record, ...
-
Well, to be clear, if you set the field's value after you submit the XML to SharePoint, the next time you open it, the value won't be what you've just set it to....
But you should be able to set the field to the value of itself concatenated with your other field - concat(Select Your Field Here, @CreatedBy)
-
Isn't @CreatedBy already in your formula? I'm confused.
-
Do you know how many characters you can have in your field that you are setting?
The formula would change to be:
substring(Your Current Formula Here, 1, Total Length Here)
-
You could use a substring formula around your concat to truncate to a specific length.
-
So, you have the Type field displayed on your form, and you can see that the value is Phone_Address and you click Submit and the rule doesn't fire?
-
These are Submit rules?
In general, if rules aren't working as I anticipate, I assume that a condition is not what I expect, for some reason. If this were my form, I'd put all the fields in play onto the form, temporarily, and see if I can determine a reason for the change...
-
Okay - that is because the lists in that Northwind SharePoint Template have columns with constraints on them. So, my guess would be there is already an Order Number 1 in the Orders table, and possibly a customer with the same ID - I'd have to check to be sure. You can either modify the lists to remove the constraints, or you can make sure you ...
-
What's the error? Did you put the QdabraRules error node on your form? What is returned there?