Qdabra qRules

Re: Qdabra GetUserProfilebyName

maysinpa — Tue, 11 Aug 2015 23:00:42 GMT

Using it as a rule works perfectly with Office 365 and an E3 license

Re: Qdabra GetUserProfilebyName

DaKanga — Mon, 09 Feb 2015 10:34:23 GMT

Hi Jim,

I looked into the other posted, but have tried to follow the instructions and wasn't able to pull the fields via the webpart. I may be doing it incorrectly. Would you be able to elaborate on the steps please?

Regarding GetUserProfilebyName I have tried executing via a button and rule and still had the same issue.

Michael.

Re: Qdabra GetUserProfilebyName

Jim Cantwell — Fri, 06 Feb 2015 16:50:21 GMT

Calling GetUserProfileByName in Office 365 has been a big problem. Here is a thread on similar issue that has a workaround for getting details in the form via web part connections: http://www.infopathdev.com/forums/p/22986/79536.aspx

Is the GetUserProfileByName being called automatically on load, or are you executing in a rule in the FormLoad event ? There have been issues with executing calls on load, so you might try executing the query in a rule.

Qdabra GetUserProfilebyName

DaKanga — Fri, 06 Feb 2015 12:04:43 GMT

I have noticed when running the command(GetUserProfilebyName) via the InfoPath client(hosted on 365), i'm able to retrieve department, username etc. When published and run as a web form on 365, I can only get the DIsplay name. Is this a limitation? If so is there any workaround to getting the users department on 365 platform.

Michael