2

We are trying to restrict the publishing of nested SG's when parent SG is published.

We tried using Custom resolver and it seems to be working fine by removing the nested SG's.

Requirement is to sometimes allow the basic behavior of publishing Nested SG's based on some conditions using some GUI option.

We are trying to integrate it using a GUI extension along with coreservices but using coreservice ,we are not able to restrict the publishing of nested SG's. Let us know if any way is there to allow both the ways based on conditions.

4

I would keep using your existing resolver and use ApplicationData (on the transaction) to store the options chosen in the UI. The resolver can then read the app data and decide whether or not to remove the child Structure Groups from the transaction.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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