Announcement

Collapse
No announcement yet.

Duplicate order

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Duplicate order

    We are using the WooCommerce integration to process sales via C&P into Salesforce. We've had an issue come up which has never happened before so I'm unsure why, but it is affecting the reports that we pull regarding sales.

    I received notification that a record was unable to post to SF so I found the order in question and tried to repost it to SF but it didn't happen. When I checked the transaction list again, I noticed that there were two transactions listed with the exact same order number; one posted to SF and the other didn't though both are listed as authorized. Because it was only one order number, I'm assuming that the info in SF is correct; however, when we pull a transaction report from C&P to check the number of items sold, both "orders" are pulled into it causing that data to be incorrect.

    Can someone please look into this so that we can be sure that this doesn't occur again in the future? Our SF instance is 00D36000000vZDF, the order number is 20940-2102201012265305003 and I've granted one week access to C&P support. Let me know if I need to do anything else. Thanks!


  • #2
    Is anyone going to help on this issue or do I need to post this in a different forum?

    Comment


    • #3
      Hi Jennifer

      My apologies, Jennifer. I had shared the order number internally with someone to review, and they said it had already been fixed.

      I will double check to see what had happened.
      Regards,
      Click & Pledge Support Department

      On Salesforce? Help us by rating our app: <a href="https://appexchange.salesforce.com/listingDetail?listingId=a0N30000003JGBvEAO" title="Click &amp; Pledge Donor Management on AppExchange" target="_Outside">Click &amp; Pledge Donor Management on AppExchange</a>

      Join us @ the educational webinars: <a href="https://clickandpledge.com/webinars/" title="Click &amp; Pledge Webinars" target="_Outside">https://clickandpledge.com/webinars/</a>
      Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: <a href="https://clickandpledge.com/webinars/" title="Click &amp; Pledge Webinars" target="_Outside">https://clickandpledge.com/webinars/</a>
      Are you on Salesforce? Join us at the Power of Us Hub: <a href="https://powerofus.force.com/0F980000000CjpC" title="Power of Us Hub" target="_Outside">https://powerofus.force.com/0F980000000CjpC</a>

      Comment


      • #4
        Jennifer,

        I only see the order once in the CONNECT, is your Patron reporting they were charged twice? The record shows it did post to Salesforce and the Opportunities for it were created on Tuesday.

        Is there still a problem?
        Regards,
        Click & Pledge Support Department

        On Salesforce? Help us by rating our app: <a href="https://appexchange.salesforce.com/listingDetail?listingId=a0N30000003JGBvEAO" title="Click &amp; Pledge Donor Management on AppExchange" target="_Outside">Click &amp; Pledge Donor Management on AppExchange</a>

        Join us @ the educational webinars: <a href="https://clickandpledge.com/webinars/" title="Click &amp; Pledge Webinars" target="_Outside">https://clickandpledge.com/webinars/</a>
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: <a href="https://clickandpledge.com/webinars/" title="Click &amp; Pledge Webinars" target="_Outside">https://clickandpledge.com/webinars/</a>
        Are you on Salesforce? Join us at the Power of Us Hub: <a href="https://powerofus.force.com/0F980000000CjpC" title="Power of Us Hub" target="_Outside">https://powerofus.force.com/0F980000000CjpC</a>

        Comment


        • #5
          I'm not sure what has happened to correct the error, but there is only one order showing now. However, I've attached a snip showing data that was pulled from the Transactions - Totals this Month report on 2/23 where you can clearly see that the order for Warren is listed twice. She did not get double-charged but there was definitely a glitch somewhere that caused this to happen. Since it appears to have corrected itself, I will consider the issue resolved for now. Thanks for your time!

          Click image for larger version

Name:	Capture.PNG
Views:	102
Size:	3.3 KB
ID:	57638

          Comment

          Working...
          X