2013 – How to show SharePoint People picker for Contact in Workflow email?

It’s by default the workflow email text can only return Login name, display name, email address and user Id number.

As a workaround, you can use Rest Api to retrieve the user profile from people picker , here is a similar post for your reference:

Is it possible to extract additional fields from people picker in a workflow

2013 – Migrate Dataview webparts in Sp2013

I’m trying to migrate the Dataview webparts which are in one of the sub site page to another subsite in same site collection through export and import option and the data is pointing to the root site list, but I’m getting the message “List does not exist. The page you selected contains a list that does not exist.It may have been deleted by another user” when adding the imported webpart.

Any suggestions/help?

Recovery Words from ~2013 Wallet Contains 4 Invalid Words

I came across my wallet from 2013 on an old external hard drive along with info like the 12 recovery words, address, etc.

I’ve tried recovering/importing it to a bunch of different wallets, but all of them are marking 4 of the 12 words as invalid and I’m confused as to how they would’ve become invalid between then and now, and how I can recover the funds in that situation.

I’m unsure what wallet/service I used to create it at the time.

Does anyone have any idea what might have happened here or how I might be able to recover this?

2013 – How to: set unique permissions for a sub-folder of a Document Set via REST

I am trying to achieve something similar to this: Break inheritance on a folder using REST below but at a level that is one deeper.

I can successfully break inheritance on a Document Set each time a new one gets added to my document library using the following REST call, as per the above answer:

https://sites/mysite/_api/web/GetFolderByServerRelativeUrl('/sites/mysite/DocLib/DocumentSetName')/ListItemAllFields/breakroleinheritance(copyRoleAssignments=true)

I can then apply successfully any new permissions that are necessary by making calls in the following format, all well and good:

https://sites/mysite/_api/Web/GetFolderByServerRelativeUrl('/sites/mysite/DocLib/DocumentSetName')/ListItemAllFields/RoleAssignments/AddRoleAssignment(principalid='XXX',roledefid='1073741826')

However there is also a sub folder that gets created underneath the document set that I need to modify the permissions on as follows (this doesn’t work but highlights what I am trying to achieve):

https://sites/mysite/_api/web/GetFolderByServerRelativeUrl('/sites/mysite/DocLib/DocumentSetName/My Sub Folder')/ListItemAllFields/breakroleinheritance(copyRoleAssignments=true)

https://sites/mysite/_api/Web/GetFolderByServerRelativeUrl('/sites/mysite/DocLib/DocumentSetName/My Sub Folder')/ListItemAllFields/RoleAssignments/AddRoleAssignment(principalid='XXX',roledefid='1073741826')

I can break inheritance and change the unique permissions on the /DocLib/DocumentSetName/My Sub Folder through the UI so I am fairly sure I should be able to do this via REST but am not able to figure out the correct call to make. Searching about hasn’t revealed much on this.

UPDATE: If I just have a folder structure in the document library such as DocLib/Folder/My Sub Folder I am able to change the permissions on the /My Sub Folder as expected by using the calls above.

Thanks

Workflow Routing in SharePoint 2013 based on a user in a dropdown list on an InfoPath Form

I have 10 entries in my workflow routing in SharePoint 2013. Each workflow routing is for a different user that will approve the workflow (Level 2 Approver). The person that will submit the form will select this user from a dropdown list on the InfoPath form. When the person submits the InfoPath form, I need the workflow in SharePoint Designer to only use the entry in the workflow routing for the user that is selected in the InfoPath form. Is this possible?

Exchange 2013 Hybrid EAC not seeing mailboxes in a second domain

We have a hybrid setup.

I have a situation where certain users are not showing up on the local on-prem Exchange 2013 server under recipients.

We have two domains in our single forest. I will call our primary domain abc.com and the second domain xyz.local.

The users in the xyz.local domain just recently were added as cloud only 365 users and this past weekend, I merged their local domain accounts with their 365 accounts and modified Azure AD Connect to sync with both xyz.local as well as abc.com. Azure AD Connect syncs are working.

The users who do not show are all in the xyz.local domain. It is like the on-premise exchange server is not aware of the Active Directory partition that contains the xyz.local domain.

I tried to modify some of the attributes in AD on some of the users in xyz.local and then they started showing up in recipients -> mailboxes in the Exchange admin center for the on-prem Exchange server.

These are the attributes I modified, matching them with attributes from a user in abc.com:

targetAddress to user@tenantname.mail.onmicrosoft.com
msExchRemoteRecipientType to 6
msExchRecipientDisplayType to -2147483642
msExchRecipientTypeDetails to 2147483648
msExchVersion to 44220983382016

I am not sure if it is just one of the above attribute changes that allows the user to start showing in the on-premise Exchange server recipient mailboxes, or a combo of attributes.

However, once the user from xyz.local shows up, I get an error if I try to view or modify any properties via the Exchange admin center (on-prem):

The call to Microsoft Exchange Active Directory Topology service on server ‘TopologyClientTcpEndpoint (localhost)’ returned an error. Error details No suitable domain controller was found in domain ‘xyz.local’. Errors: .

I am wondering if you might have any advice. It seems like maybe the on-premise Exchange server just needs to be made aware of xyz.local. I did a lot of searching and have not been able to figure out if there is a setting in EAC or a PowerShell command that I should run in the Exchange Management Shell. Any help would be much appreciated.

InfoPath Filler 2013: How to resolve ‘This form cannot be opened because it requires the domain permission level…’ error

I have an InfoPath form stored on a network drive that submits to a SQL database. A few years ago, when updating from 2010 to 2013, users started receiving the following error when attempting to open the form in filler:

“InfoPath Error: Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code.”

"InfoPath Error: Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code."

Over the years, the issue has been sporadic and we haven’t been able to pinpoint the cause or a permanent fix. We’ve scoured the forums, and have attempted many recommended fixes, but none seem to fully resolve the issue. Does anyone have any recommendations? Here’s what we’ve tried so far:

  1. Reviewed SQL database and network drive permissions.
  2. Updated InfoPath form Security Level from “Automatic” to “Domain” permissions.
  3. Attempted to update Security Level to “Full Trust” (but disabled by Admins).
  4. Digitally signed the form template with a valid user certificate.
  5. Published form to a different network path under a different name.
  6. Published to a SharePoint site.
  7. Updated form compatability settings from InfoPath 2010 Filler Form to InfoPath Filler Form.
  8. Updated form versioning settings to “Automatically update template” and “Automatically upgrade existing forms”.
  9. Cleared InfoPath cache using RUN command: InfoPath /cache clearall
  10. Updated Trust Center Settings by deselecting “Check Microsoft Office documents that are from or link to suspicious Web Sites.”
  11. Full review of form to ensure any rules used Fully Qualified Path, instead of network drive shortcut.
  12. Instructed form users to open form in Design mode, then “Preview” the form.

The only one that has worked, has been (item 12) for users to open in Design, then click preview. We do not want our users opening the form in Design mode. Any suggestions?

I am unable to create new workflows using sharepoint designer 2013 on new site collections

I am unable to create new workflows using SharePoint Designer 2013 on new site collections.

When I check for errors I am getting All tasks that need to have at least one outcome defined. And when I check to see the task information, there are no items in the Task Outcomes section.

SP environment: SP 2013
Workflow platform type: SharePoint 2013 Workflow

Does anyone have a solution to fixing this?

enter image description here