This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DisableRequiredFields_SPItems_BeginTransformation_V2 & DisableRequiredFields_SPItems_EndTransformation_V2 Transform Question

​We have been using these in one set of migrations where we migrate individual sites. If required field errors are generated we run an incremental using these transforms as needed. Our next migration is big bang and will involve 255 sites. We won't have the luxury of evaluating logs and rerunning. In looking at errors involving these scripts we notice that they need to be configured at the item level which would be a performance killer. We want to be sure it needs to be this way, Logic says that it would be better to operate at the Lib level.

 

1.) Make lib ContentType all fields non-required

2.) Migrate lib contents

3.) Reset lib ContentType back to original state

 

We assume Yogi wrote it at the item level for a  reason but wanted to be sure we understood before proceeding.

 

Thanks,

Doug

Parents
  • Thanks Cyrus, So the first comment in the script says… # SharePoint Items Begin Transformer This implies that the script operates on the item level and that is how we configure the transform. Are we to configure the scripts at the list level? We have been configuring at the item level. Should we at list level? Thanks, Doug [cid:image002.png@01D45A43.26D46770]
Reply
  • Thanks Cyrus, So the first comment in the script says… # SharePoint Items Begin Transformer This implies that the script operates on the item level and that is how we configure the transform. Are we to configure the scripts at the list level? We have been configuring at the item level. Should we at list level? Thanks, Doug [cid:image002.png@01D45A43.26D46770]
Children
No Data