Loyalty Notification Duplicate SMS Issue

Loyalty Notification Duplicate SMS Issue


# For Internal purpose


Product Version:  

iVend 6.6  

 

Problem Statement:

Loyalty Notification issue Duplicate SMS

  

Proposed Solution/Workaround:

It might be possible due to there being multiple notifications set up for Points Expiry, even if it is deleted. You can check the same using below SQL query. This is filtered out for the deleted notifications in the latest files.


select IsDeleted, * from LoyNotification where Event = 6


Constraints/scenarios:

 #CS0005042



    • Related Articles

    • Multiple SMS for single Loyalty Transactions

      Environment : iVend Version 6.6 with SAPB1 9.2 Problem Statement: Multiple SMS for single Loyalty Transactions Symptoms : Multiple SMS for single Loyalty Transactions Resolution/Work Around : Due to SMS gateway ,not returning the success message, the ...
    • Loyalty Notification - Mail and SMS

      Loyalty Notifications - Mail and SMS iVend Retail versions 6.5 and above supports notification by Email and SMS to end customers. The notification is triggered by and event or by interval, such as a New Loyalty Customer being created, Points about to ...
    • SMS Notification Sample

      Introduction iVend Add-on Framework is used for writing Custom Business Logic independently by a programmer. iVend Addon allows to extend business logic either in Management Console or at the Terminal POS. The addon framework allows deployment of ...
    • SMS Integration

      Introduction SMS Integration in iVend Retail provides Retailers, the flexibility of receiving iVend Reports or results of a SQL Query via email, by simply sending a SMS from a registered mobile number. Using this feature, Retailers will just need to ...
    • Customer's are not receiving SMS, after a sales transaction

      Environment: Not Environment Specific Product Query: After a sales transaction, SMS should be triggered to customers. After the completion of the EOD process, an EOD SMS should be triggered to MD. Response: The requested functionalities do not exist ...