pnp / pnp/pnpframework

ContactFieldControl not identified during transformation

Open
#453 5 comments 0 reactions 1 assignee View on GitHub

@jansenbe is already working on this.

Since Sep 3, 2021.

area: page transformation 🦾
Dominant language
C#
Stars
259
Forks
161
Avg merge
10h 33m
Merged PRs (30d)
1

Description

I'm doing transformation from SharePoint 2013 towards SPO of a page that holds ContactFieldControl webparts.
The transformation logs below mentions the error that it does not recognize the Contact details webpart as a ContactFieldControl (Title is Department Manager). If I export the dwp file from the page it holds the correct TypeName and assembly for the v2 webpart

Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
Microsoft.SharePoint.Portal.WebControls.ContactFieldControl

I dont see a reason why it wouldnt work. The transformation is succesfull besides the warnings about these contact webparts. Other webparts like listview and CEWP are correctly transformed.

30/08/2021 13:38:25 | Input Validation | Validation checks complete
30/08/2021 13:38:25 | SharePoint Connection | Loading client context objects
30/08/2021 13:38:25 | SharePoint Connection | Loading target client context object
30/08/2021 13:38:25 | Page Creation | Detect if the page is living inside a folder
30/08/2021 13:38:25 | Page Creation | In Cross-Site transform mode the original source file name is used
30/08/2021 13:38:25 | Page Creation | Just try to load the page in the fastest possible manner, we only want to see if the page exists or not
30/08/2021 13:38:27 | Page Creation | The page already exists in target location
30/08/2021 13:38:27 | Page Creation | Modern page created
30/08/2021 13:38:27 | Article page handling | Transforming source page as Article page
30/08/2021 13:38:27 | Article page handling | Recognized source page as a Publishing Page - Analyzing web parts and page layouts
30/08/2021 13:38:27 | Page Layout Manager | Page uses ASMLDWExtendedPageLayoutMenu as page layout, mapping that will be used is ASMLDWExtendedPageLayoutMenu
30/08/2021 13:38:27 | URL rewriter | Loading URL mapping file C:\AzureDevOps\myASML2.0\myASML2-Migration\ToModernSPO\Source Files\urlmapping_EDEV01.csv
30/08/2021 13:38:28 | Content Transform | Calling Web Services to Extract Web Parts from Page
30/08/2021 13:38:31 | Content Transform | Source page contains web part Welcome to the Electronics Development DUV Homepage of type Microsoft.SharePoint.WebPartPages.ContentEditorWebPart
30/08/2021 13:38:31 | Content Transform | Source page contains web part Content Editor of type Microsoft.SharePoint.WebPartPages.ContentEditorWebPart
30/08/2021 13:38:31 | Content Transform | Source page contains web part News of type Microsoft.SharePoint.WebPartPages.ClientWebPart
30/08/2021 13:38:31 | Content Transform | Not Supported, Non Exportable or Unidentified Web Part
30/08/2021 13:38:31 | Content Transform | Source page contains web part Department Manager of type Unsupported Web Part Type
30/08/2021 13:38:31 | Content Transform | Not Supported, Non Exportable or Unidentified Web Part
30/08/2021 13:38:31 | Content Transform | Source page contains web part Management Assistant of type Unsupported Web Part Type

@jansenbe

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.