-
There isn't. If you copy the view by selecting everything and pasting it into your new form, you'll have to rebind all the controls to the new form's schema. Generally it is just simpler to recreate it.
-
Sorry - I was looking for default values instead of at rules! Your XPath is incorrect. The correct condition for Rule 1 on HoursNewStatus would be: substring-before(xdDate:AddSeconds(xdDate:AddDays(../my:SubmitDate, substring-before(., ";")), 0), "T") != substring-before(../../my:Credit/my:CreditOwnerAssignedDate, "T")
-
Do you have a copy of this form where you've tried to implement the logic you've linked to? You originally posted a screenshot that showed a rule inspector issue.
-
I'm looking at the HourDifference file you attached - and I don't see the field in your screenshot. I don't know how to help you figure out the issue when the screenshot doesn't match the provided form? Or is it a different form? When you say the forum won't "let" you attach your form - can you tell me what error you ...
-
Is this from a published form? I was pretty sure that SharePoint Online no longer supported browser forms with code - which rules out qRules in browser forms for sure. I'm assuming that you cleaned up the URLs above to remove your company info. For SharePoint online, we recommend using FormsViewer which will allow you to keep using your ...
-
Drag the data fields from the data connection onto your form so you can see the returned data.
-
Well, it could be that it is going to the admin view, but the rule following that is switching it back to the requester view. It could also be a rule order issue. I'd probably disable some of these rules and verify that the switch to admin view was working, then start trying to figure out when to go to the requester view. I'd also guess ...
-
You've got the permissions on the list configured as per the blog post? I think I'd probably put the SecurityLevel data connection on the form some place (in both views) so you can see what data is being returned and whether it is what you'd anticipate. I'm also confused by your post - what is currently happening in the form? What ...
-
Perfect, glad you got it figured out. So SharePoint stores dates as datetime. Even if you have the format set on the field to display only date - it is still datetime. That's why the time portion is included! But if you strip off the string from the T on, as you found, you get the date value. String-compare works (which if you look at the ...
-
Yes, they can all be in form load. Just be careful if you have any form load rules that may change that field's value - you'd want your rules to switch the view to run before it could be changed.