{connection/event:aConnection/anEvent} calls earlier version aConnection

I have a a call to a connection so:

{connection/event:ManageMemberPartners/index}

As I develop connections I take a new copy from time to time, leaving earlier versions available to cover my butt.

A problem has arisen in that if I run the latest version (say id 66) then that connection call loads the earliest version (say id = 60). If I delete all of the earlier versions then the all works fine.

Nick

Hi NickOg,

Typically CC (and CF) identify forms by name, not by ID, so you should rename the old forms when you create a new copy (and probably disable/unpublish them too).

Bob

Morning to you both.

Yes, of course one can deal with that as you suggest but this is quite a change from CC5 & CF5 where I have used the technique I described for many years. Threw me for a while!

Nick

Hi Nick,

Even in v5 you should not have forms with the same name, and if it did work then because the latest form had the highest id.

Best regards,
Max

Hi Max

Indeed not and in my production site that is the case.

I think your last point is the key - in CC5 and CF5 it always loaded that form/connection with the highest id where there were multiple forms with the same name whereas in CF6/CC6 it loads a form/connection with the lowest id where there are multiple forms with the same name

Nick

Hi Nick,

True, but still it is not advised to rely on this, you should have unique names for v5, and alias for v6 at all times.

Best regards,
Max

Got it. In hand now. 🙂
Nick