Re: userName() issues with claims

javicartin — Wed, 07 Sep 2016 23:11:13 GMT

Hi, I changed the rule condition from is not equal to to do not contains and it is picking the username and it is working by now, thank you

userName() issues with claims

javicartin — Wed, 07 Sep 2016 22:28:25 GMT

Hi, I am having this issue with claims and the username value.

We have an InfoPath form created on 2003 version, then, it was moved to SharePoint 2007 and now to SharePoint 2013. On SharePoint 2007 and InfoPath 2007 we had the field currentUser with default value userName(). Now on SP2013 we are using claims authentication, so, when I add this field currentUser to the form , I got this on the form; ´ , see attachment with images.

We had an issue when hidden a button and the solution was to add a rule with this format, previously we only had the value like jcartin. And the solution was to add the claims format in order to fix the issue.

Now, we are seeing that this claims format is affecting other rules, for example, we had some rules to hide - disable a field and this is not working anymore, for example, this rule persue to gray-out a field, this is the rule configuration,

The rule is seeing a value in a field which is based on a data connection pointing to a SharePoint list in the site where we have users as items including columns like name, username like jcartin.

Any idea of what format or rule configuration can we use to point to the old format like before for example, the rule to interpreter username as jcartin and not i:0#.w|domain\jcartin , thank you.

General

Re: userName() issues with claims

userName() issues with claims