How do I solve a circular dependency. I have 'permissions' in a custom record that references a custom role .. and that custom role, in turn, references the custom record. Removing permissions or references on either side end with errors

What's the exact error you're getting? I've deployed without issue a custom record and custom role with the custom record's access. Could it be with how your deploy is configured?

So, the custom record references a role and defines the permission it has ... and that role references the custom record it has access to. That's where the circular dependency is. However, if I remove the permission definition from the custom record, the role complains (errors out) and if I remove the custom record reference from the role, the custom record complains (errors out). So, I can't win.

what's your deploy.xml look like?

Not sure why/how the

deploy.xml

would affect this ... it simply states

<objects>
    <path>~/Objects/*</path>
</objects>

this is the permissions in a custom record

<permissions>
  <permission>
    <permittedlevel>FULL</permittedlevel>
    <permittedrole>ADMINISTRATOR</permittedrole>
    <restriction></restriction>
  </permission>
  <permission>
    <permittedlevel>FULL</permittedlevel>
    <permittedrole>[scriptid=customrole_nact_administrator]</permittedrole>
    <restriction></restriction>
  </permission>
</permissions>

Then also in a custom role

<permissions>
<permission>
  <permkey>[scriptid=customrecord_nact_task]</permkey>
  <permlevel>FULL</permlevel>
  <restriction></restriction>
</permission>
</permissions>

I'm assuming yours is similar?

Exactly

I get warnings but it still deploys fine

So do I ... I'm looking for get a clean (no errors or warnings) deployment.

It throws a circular dependency warning for so many things but I don't think that is really an issue as it can still deploy successfully. Oh I don't think you'll be able to get rid of the warnings

I assume a warning means a potential for something bad .. otherwise, why warn?

not sure... i'm confused as to why they show them

Ok, so ... end of the day, its fine to ignore those warnings then. Ok

Yeah i have been. I have the same issue with sublist searches that I deploy or subrecords