[Sage X3 multi-tenant cloud sandbox]

On 3/2/2022 at 1:48 AM, JREWCASTLE said:

I have read articles on Sage's website:

Now available for purchase a lightweight Sage X3 multi-tenant cloud sandbox to support the needs of Sage’s X3 developer community

From <https://developer.sage.com/x3/announcements/2021-02-05/>

300 templates available with Data Integration API for multi-tenant cloud

https://developer.sage.com/x3/announcements/2020-10-13/

I can't find where I can purchase a Lightweight Sage X3 multi-tenant cloud sanbox

or a list of the 300 templates available for Data Integration API

 

Any help will be appreciated.

 

 

 

I am also looking for this . 

[Creating posted AP Payment via XML API]

It's unlikely that the issue you're facing is related to permissions. While the API allows creating payments, it doesn't directly control whether they are listed under "Posted payments" or "Payment requests." Here's what might be happening:

1. Payment Submission vs. Posting:

The API endpoint you're using, create-ap-payment, primarily creates a draft payment. This means the payment is not automatically finalized and reflected in your accounts. To achieve "Posted payments" status, you typically need an additional step to "submit" or "post" the payment.

2. Checking the API Documentation:

The documentation for create-ap-payment mentions a parameter called "Submit" with a default value of "true". However, it doesn't explicitly state how submitting the payment affects its status. You might need to check if there's any specific endpoint or action within the API to officially "post" the payment and move it from "Payment requests" to "Posted payments."

3. Considering Alternatives:

If submitting through the API isn't readily available, you might explore alternative approaches:

• Marking the Payment as Paid: Depending on your integration with the third-party provider, you might be able to send a signal back to Intacct indicating the bill has been paid. This could involve updating the relevant bill record with a "paid" status or triggering a separate workflow that updates the payment status internally.
• Custom Development: If the above options don't work, you might need to consider custom development. This could involve building a custom integration that interacts with the Intacct API to not only create the payment but also handle the posting process through additional API calls or internal workflows.

Remember, for definitive answers about posting payments through the API, it's recommended to:

• Consult the Intacct Developer Portal: The official documentation for the API might have specific instructions or examples for posting payments.
• Contact Intacct Support: If you still face issues, reaching out to Intacct support could clarify the functionalities and steps needed to achieve your desired outcome.

[New to the Sage Developer Community? Introduce Yourself!]

Hi, I am Brain John, I am new to sage community.