0

We have SharePoint 2016 and like to create some central maintained lists (a country list, flags, locations of our company, contacts etc.).

Since we have a workflow that clones a list to a different Site Collection, it was my idea to delete the list on the target Site Collection (by workflow) and then just copy it, if something changes on the source Site Collection.

The problem seems to be, that lookup values are referenced via list GUID, so other lists who used that cloned list will fail, since the list GUID is different.

Does anybody have an idea how to solve that?

Improve this question

1 Answer 1

Reset to default
0

if you switch from using workflows to deploy your lists to for example PnP PowerShell you should be able to keep a central template using PnP Templates. That should be able to maintain your lookups and update fields accordingly. if that's not enough you can even write c# code using Extensibility Providers

if for whatever reason you have to keep workflows, how about a custom workflow action to update your fields references with code?

Improve this answer
1
  • Unfortunately we have strong restrictions at the farm. The workflow solution we use (ShareFlex) is the only option for server side code.
    – Dave
    Commented Dec 18, 2020 at 15:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.