Losing custom formatting for list migration #74
Answered
by
Zerg00s
harveryang
asked this question in
Q&A
-
This tool is undeniably effective for migrating PowerApps and Flows associated with lists. However, I observed that when a list incorporates custom formatting—such as a custom style applied to a column or view—the custom style JSON loses its original format, resulting in a disruption to the custom formatting. Is this a known issue? Anyway to workaround it? |
Beta Was this translation helpful? Give feedback.
Answered by
Zerg00s
Jan 19, 2024
Replies: 1 comment 6 replies
-
Hi @harveryang. Yes, I saw this problem before. Let me have a look at it. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You are right. The only issue is that the PnP.PowerShell module won't work without the Azure App registration or at least the SharePoint-only app. Most users are not M365 Tenant Admins or even SharePoint Admins. This is the reason I chose to use the legacy module. The legacy module works with the good old browser-based authentication, with a pop-up window. I really need to think about what to do next. So far, if the column formatting is the only issue, it's not worth the upgrade yet.