You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First post, apologies if I am not clear.
We have built a site in SPO (Client Dev tenant) and used PnP to pull that site, settings, layouts and content types to deploy to a SPO Prod tenant (Client).
We are using Document sets, with a shared column of "Meeting Date" - that is supposed to inherit on all content inside the Document Set -
That Meeting Date column is used to calculate the YEAR as part of the build for views, etc in the Library.
Works here: (Original site, and ONE site that it did work on when deployed in Production)
Not here: (NEW site created in Dev to test, and on 3 other sites - totally different tenants, and one site in Production
We tested the same PowerShell on 7 other sites, 4 different tenants - it worked 3 times, and the other 4 times it did not.
We have copied the Content Types to Production, and pointed the Powershell to that location (in case it was an issue - and still isn't working as it should).
I am able to create a Library on the Production tenant, create a NEW Document Set Content type and use the site columns already there, and use the same settings - and it works
(NOTE: I am not a dev, I did not write the powershell / xml - but did build and test the SPO build.
Has anyone experienced this, or have any advice to troubleshoot?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
First post, apologies if I am not clear.
We have built a site in SPO (Client Dev tenant) and used PnP to pull that site, settings, layouts and content types to deploy to a SPO Prod tenant (Client).
We are using Document sets, with a shared column of "Meeting Date" - that is supposed to inherit on all content inside the Document Set -

That Meeting Date column is used to calculate the YEAR as part of the build for views, etc in the Library.
Works here: (Original site, and ONE site that it did work on when deployed in Production)

Not here: (NEW site created in Dev to test, and on 3 other sites - totally different tenants, and one site in Production

We tested the same PowerShell on 7 other sites, 4 different tenants - it worked 3 times, and the other 4 times it did not.
We have copied the Content Types to Production, and pointed the Powershell to that location (in case it was an issue - and still isn't working as it should).
I am able to create a Library on the Production tenant, create a NEW Document Set Content type and use the site columns already there, and use the same settings - and it works
(NOTE: I am not a dev, I did not write the powershell / xml - but did build and test the SPO build.
Has anyone experienced this, or have any advice to troubleshoot?
Beta Was this translation helpful? Give feedback.
All reactions