I need to send my code that is in the test environment to the production environment, however, there are some group identifier errors. I do not make sense.
Can someone help?
Begin transport. 2024-04-12 14:29:41.99 DEBUG group 61 20a13bee-28e1-4b24-a02e-21ee270d3116 Loop detected: [group:61, group:160] 2024-04-12 14:29:41.99 DEBUG group 61 Breaking loop [group:61, group:160]. group:160 will be transported with its reference to 61 nulled out and will require a second pass.
Discussion posts and replies are publicly visible
Hi Luiz Braido we need more context on this , how are trying to send your code from test to prod env , which object deployment is throwing this error
PROD is empty, this is the first DEPLOY.
I'm trying to send the code COMPARE AND DEPLOY, it doesnt find any error on inspection, but when I deploy it fail. Do not show where is the problem.
What do you get when you run Missing Precedents Checker? I'm assuming by the above issue that it won't come up empty for you if you run it. That would be the first clue.
That's not the Missing Precedents Checker. You'll need to access that from the app (or package) itself prior to opening the Compare and Deploy interface.
Also: i look at your error message again and I can see it's because you have 2 groups that both include the other as a member (hence the "loop" warning). You'll need to correct this then deploy. Or deploy anyway and see if it works - the message seems to indicate that the deployment mechanism might just auto-correct for this. What happens when you try?
Auto-correct just fail
So u think that the problem can be a group inside the other?
Luiz Braido said:the problem can be a group inside the other?
Yes, as I said, the error message is telling you that Group 61 and Group 160 both contain the other as a member.
When you say "fail", what happens exactly? It already says you will need to make 2 passes (i.e. deploy twice) if you want to keep the membership loop - so I'd guess, based on that, that a second deployment will report a success (though it may not work, in which case you'd probably just need to break the loop manually first).
What's your use case for having a loop within the group? There's a reason this doesn't work - it's not good practice to have a loop of groups that reference each other.