-
The distinguishedName key provides a concatenation of comma seperated values. You can use string-before(string-after(<field>, ''CN=''), '','') to pull out the particular value you are looking for.
However, if you place a repeating table on your view bound to the repeating ADProp group from the web service, it will show you all the key value ...
-
I've moved this discussion to the Qdabra AD WebService forum...
Yes, you should be able to filter using the key/value pairs, as described before, to get the value you want. I don't have the exact xpath for you, but you should be able to decipher what I wrote earlier to understand how to get the value you want. If you have further specific ...
-
Maybe I don't understand your scenario well enough... but you mentioned using ''part of a rule''. I take that to mean that are using the Rules feature available on fields. If that is the case, there is a condition portion of a rule that must be met before any actions occur. It is there that you can do your if/else. Just make sure that on the ...
-
Sure. I hope that worked for you!
-
Which webservice are you referring to?
I'm assuming you have key/value pairs. If so, then you get the webservice/returnvalue/value[../key = 'CN'] --or equivelent-- webservice/returnvalue[key = 'CN']/value
-
Sounds like what you need is conditional formatting.
Have both fields present in the view. Then add conditional formatting to fielda which hides it if its value is greater than or equal to the value in fieldb. Add conditional formatting to fieldb which hides it if its value is greater than fielda.
-
Do you have multiple rules on your field? If so, you might try adding an rule which pops up a dialog box stating ''action passed'' or something, and check to box to stop processing rules when finished. Then you can move this ''debug'' rule up and down to figure out at which point the rules are failing. That will narrow it down.
-
You can only do this through conditional formatting. Conditional formatting should allow you to disable based on a user role.
Having said that, if you create a field, and use conditional formatting based on the value of that field, you can use code to change the value of the field which will then affect your conditional formatting--effectively ...
-
Hi.. again, I'm glad you got it working, and not having it as optional is a satisfactory solution, then there's no sense going back to it at this point.
I'm not exactly sure why it wasn't working for you--I just know that I do this kind of stuff all the time and have never had such issues. All I can think is that there was some other issue ...
-
Something more like:
Team_Members/@Employee_Email_ID[../@Employee_Name = xdXDocument:get-DOM()/my:myFields/my:Emp]