CC saves data twice but only once with CF

I hope I am overlooking something really simple😃

I have created a CF document that works well and saves the data as it should. I then created a CC document for the results of this data with functions to add, edit and remove.

I have noticed that when clicking 'add' on the CC document, the corresponding CF document will save the data twice and thus requires the second entry to be 'removed'.

Have I overlooked something?

http://easyentry.co.nz - create a new user and 'My NZKC Membership #'s' link will take you to the CC document in question.

Hi j.crilly,

That link doesn't appear (unless I register and log in I guess) and I'm not sure that it would help. I'm working on a CC project now and will see if I can replicate this.

Bob

I just got duplicate entries after using the "new record" for the CC front end. (/chronoconnectivity/?connectionname=adminRegistrations&task=newrecord)

I'm using the edit form as the same CF that users use to register for the conference. I figure this way I don't have to have two forms to update if there's a change🙂

I guess your add link is "{new_record}"?

Do you have emails set up on the CF? Do you get two emails too?

Hi Jessica,

I am using the {new_record} as you and cannot for the life of me work this one out. Hopefully Bob can come up with a quick fix. I do need to build in a check for duplicate entries, but at this stage not too worried with an extra step.

I do not have emails set up as this will potentially make for 100's - 1000's of emails a day when up and running, although to check it would be interesting to see.

Cheers
Jamie

Hi,

Just wondering if any solutions or paths to check have been thought of...Bob? Jessica?

Cheers
Jamie

I had the same problem but when I disabled data storage for the form in CF the record only gets recorded once.

When I disabled data storage it'll just save nothing

Getting the same thing on this end. Evaluating ChronoConnectivity today for a project. Have run into a number of issues.

1) Upon using the {new_record} front-end method to create a new record, an exact duplicate is created identical to the first, with the exception of the cf_id field, which is incremented one more (as one would expect). Possible deal breaker, but for this particular project I don't need a front-end method to add a record (where). Still troubling.

2) Also upon using either the {new_record} or {edit_record} methods, if the original CF form was designed to send emails, then the CC addition/edit also fires off those emails. Groan. This can be mitigated by simply duplicating the original CF form, and disabling the emails. Causes the form to be maintained twice, but is workable. Not a deal breaker.

3) The front-end field sorting (mention elsewhere in this forum) was another mystery. There is a place to enter values for front-end field sorting, but apparently no functionality here. Not a deal breaker. Can work around this per GrayHead's suggestions in other threads.

What is the status of development on the CC project? Not getting the impression is it actively developed.

Thanks,
Brad =)

Hello All,

If your Chronoform used has "DB connection" enabled then Chonoforms will trigger a save and Connectivity will trigger another one by default resulting in 2 records

Brad,

#1- above ^^
#2- yes, same theory, some may love this, please create another form without emails
#3- you mean a sortable list in the frontend ? or just an ordered one ? if its the 2nd one then you can add "ORDER BY" statement to the WHERE SQL piece

I wanted to improve all our extensions a while back but thought it would be better to wait till J1.6 is out since it should come with many improvements, so you can expect some updates once J1.6 is RC3 or stable, hopefully sometime soon

Regards
Max

So whats the solution...

I just turned off my form DB storage and now I only get one entry. Any draw backs when doing this?

Hi Andrew,

My personal approach is not to use the {edit_record} and {new_record} syntax but to build a url link to the ChronoForm. That avoids both problems 1 & 2.

Bob

Bob,

That is a solution.

However with the current form I use, an email is generated when the form is submitted.

Maybe a better solution would be creating a duplicate form with no emails being generated. Then I could just link to the duplicate form.

Thank you, for your input.

Hi Andrew,

However with the current form I use, an email is generated when the form is submitted.

I don't see how that causes any problem. The email is still sent however you access the form?

Duplicating the form will work OK - I try to avoid doing it unless absolutely necessary as it increases the maintenance needed if any changes are required.

Bob

Thank you as always kind sir.

Hi!

I'm fighting with the same issue and that is how I solve it. When I create the form I don't set a redirect url, setting it solve the problem.

I hope it will be usefull😉