Please see the attached image. I have faced the problem of creating COC with 19 parameters of ISV. So this type of issue was not faced before.
Yeah, But we all know that event handler is not the best practice in that case event handler is the only solution, but I need to find out why COC is not created for that method :(
That the reason is to raise question here!
Thank you both of you
Really appreciate your response!
But there is no such documentation available to confirm this.
Thanks,
Girish S.
Your CoC method looks fine, as Girish suggested you can write event handler and if build pass then all good.With 19 parameters event handler is better choice in terms of code readability.
Yeah, I think so but I need official documentation about that to share with our community If there is nothing wrong in COC.
There is no problem with the implementation of the COC you have written.
My suggestion is methods parameter is too long in your original method. May be there is some restriction in the number of parameters when using COC, but I am not sure on that.
Thanks,
Girish S.
Yes, This one is, I already do that for Azure DevOps build passed!
But I want to figure out what is the issue in COC and What am I doing wrong in COC?
Is there any limitation or something else?
Then the only solution will be adding Pre and Post event handler for the method "AutoCreateDebit" to meet your scenario.
Thanks,
Girish S.
I don't think there is limitation in the method arguments while using COC.
One option will be reducing the parameter to below 17 by changing the original logic and check.
Another option will be try passing only the required parameters, omitting the optional parameters in the COC.
Thanks,
Girish S.
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,817
Most Valuable Professional
nmaenpaa
101,156