Jump to content

Rafał Pająk

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

 Content Type 

Posts posted by Rafał Pająk

    SageOne API 3.1 - Contact Payments identified by public Id are no longer accessible by API

    in Bug Reporting

    Posted

    Steps to recreate:

    1)   In SageOne I import bank statement 

      2) In SageOne I ‘transfer’ this bank statement to PaymentOnAccount


    3) At this point I can get contact payment under API url using 'old id' 'id1111' - scything works as expected
    https://api.accounting.sage.com/v3.1/contact_payments/id1111

    4)     In SageOne I’m partially assigning 450 GBP from this payment on account to Invoice SI-7

    5) After this operation is completed new payment object is created with 'new id' 'id2222'
    And it can be access under url     https://api.accounting.sage.com/v3.1/contact_payments/id2222
    This is also ok

    6) But the problem is that the old one payment object is no longer visible at all
    6.a) Not visible under   https://api.accounting.sage.com/v3.1/contact_payments/id1111 
    6.b) Not visible under https://api.accounting.sage.com/v3.1/contact_payments?deleted_since=2024-01-01T00:00:00Z

    Current state:
    For some Contact Payment objects return under public id are no longer accessible by API (after some operations on UI)

    Expected state:
    Even if Contact Payments objects are created (using new public id) all previously returned public id should still be available under one of urls
    - https://api.accounting.sage.com/v3.1/contact_payments/id1111 
    - https://api.accounting.sage.com/v3.1/contact_payments?deleted_since=2024-01-01T00:00:00Z

    Extra questions:
    1) Is it possible that similar behaviour can be result of different modifications to Contact Payments on UI? 
    2) Is it possible that similar behaviour can be visible for other objects form API like Sales Invoices, Credit Notes, etc?


     

×
×
  • Create New...