Hello,
is it possible to show a single entry from a database only once and mark this as "read" (or delete that entry or something else)? The entries in the database are vouchers that can be used only once.
For this reason, the vouchers may not be repeatedly displayed.
The form is already created, the database contains the coupon codes. What should I do next? Using Chronoforms with DB-loader or better ChronoConnectivity?
Since my php skills are very low, I'm grateful for any hints or suggestion.
Thanks in advance!
is it possible to show a single entry from a database only once and mark this as "read" (or delete that entry or something else)? The entries in the database are vouchers that can be used only once.
For this reason, the vouchers may not be repeatedly displayed.
The form is already created, the database contains the coupon codes. What should I do next? Using Chronoforms with DB-loader or better ChronoConnectivity?
Since my php skills are very low, I'm grateful for any hints or suggestion.
Thanks in advance!
Hi Tomelly,
I'd use a ChronoForm as there is only one record to display. You need to think through the logic of this carefully to avoid issuing the same voucher twice. Is it 'used' once the user views it? Or do they have to do something to accept it? Do you link a particular user to the voucher - or just rely on the voucehr code to identify them?
Bob
I'd use a ChronoForm as there is only one record to display. You need to think through the logic of this carefully to avoid issuing the same voucher twice. Is it 'used' once the user views it? Or do they have to do something to accept it? Do you link a particular user to the voucher - or just rely on the voucehr code to identify them?
Bob
Hello Bob,
thanks for the fast reply.
Once the vouchers have been displayed, they are no longer needed.
Perhaps I should explain briefly ... The vouchers will be issued as a discount to our customers. The redemption is in the shop. In the store-database the coupon codes are stored separately.
There will also be tested if they are still valid or has already been redeemed.
The coupon codes are shown only to employees, not the customer directly. Currently the allocation of codes is performed manually through an Excel-File (Staff opens the file, cut out the code and save the file)
The problem is, that the staff forget to cut out the coupon code - so the next staff-member can hand out the code again.
Do you think, I can realize this with the DB-Loader?
thanks for the fast reply.
Once the vouchers have been displayed, they are no longer needed.
Perhaps I should explain briefly ... The vouchers will be issued as a discount to our customers. The redemption is in the shop. In the store-database the coupon codes are stored separately.
There will also be tested if they are still valid or has already been redeemed.
The coupon codes are shown only to employees, not the customer directly. Currently the allocation of codes is performed manually through an Excel-File (Staff opens the file, cut out the code and save the file)
The problem is, that the staff forget to cut out the coupon code - so the next staff-member can hand out the code again.
Do you think, I can realize this with the DB-Loader?
This topic is locked and no more replies can be posted.
