Restore specific member

[bjarnef]

I tried the restore member option recently added to Umbraco Deploy:
https://docs.umbraco.com/umbraco-cloud/deployments/content-transfer#members-and-member-groups

However member doesn't allow to restore a specific member as content and member does.
Furthermore the content and media restore of picked item doesn't look consistent.

Content

Media

Member

[bjarnef]

@AndyButland would it be possible to add option to restore a specific selected member from remote environment?

and streamline the UI in content, media and member restore dialog?

[ronaldbarendse]

Hi @bjarnef,

Both parts of this are handled in Deploy 17.4 and 18.2.

Restoring a specific member. Partial restore is no longer limited to the entity types that shipped their own remote tree. Members and member groups now have the same "pick a specific item to restore" action as content and media, both on the tree root and on an individual item, and you can pick any item that exists on the remote environment, including one that doesn't exist locally yet. Dictionary items get it too when they are transferred as content (Umbraco:Deploy:Settings:TransferDictionaryAsContent).

Consistency. The three separate remote trees behind content, media and "other entities" have been replaced by a single one, so the dialogs now look and behave the same regardless of what you are restoring:

• Picking uses the standard backoffice tree picker, with a placeholder-style button that matches the core pickers and a uui-ref-node for the picked item. There are screenshots in Partial restore of form doesn't select form #330 (comment).
• The picker's search field searches the remote environment, so you can find an item by name at any depth instead of expanding your way to it. For members it matches the name, username and email.
• Items are fetched in pages instead of a whole level at once, which also helps with the large trees in Tree picker in partial restore should use mini list view for nodes configured as list view #314.

Packages that register their own entity types keep working through a generic fallback, and can opt into paging and search by implementing the new tree connector interface.

Thanks for the reports and the screenshots, they made this much easier to scope.