@ToddWhaley can you please direct message me your Customer Care Case #? 

thanks, Dana

Acumatica Case ID# 339667.  Thank you.

@ToddWhaley i have asked the customer care rep to reach out to you with the resolution.

Thank you @Dana Moffat.  I appreciate your help!

@Dana Moffat The person that reached out to me has not responded to my last email.  Can you have someone reach out to me with answers please?  Thank you.

Hi @ToddWhaley thank you for reaching out.  I have let the support escalation manager know of your customer care case and the problems you’ve been having.

Thank you @Dana Moffat.  This is creating major issues for our operations and accounting teams.

Todd

Hi @ToddWhaley were you able to find a solution? Thank you!

We are working with Acumatica and True Commerce support currently.  So far, no resolution.  Thanks for asking.

Hi

I have been using True Commerce for quite sometime now, can you share more details of the issue?

Are you logging in from Acumatica into Foundry, or Foundry is logging in to Acumatica?

You can private message me the case details if you don't want it all on the forum.

Hi ​@schneur96 

A product update was provided by True Commerce for the support case mentioned by ​@ToddWhaley .

The updated package resolved the issue and the case was closed.

-Dana

Per True Commerce this is normal behavior for 23 R1 integration with True Commerce.  The integration logs the integration out every 30 days.  This is resolved in later versions of Acumatica.

Are you referring this login screen TC103000?

​@ToddWhaley 

Yes, that is the screen where we need to authenticate every 30 days to the True Commerce Integration.

Got it.

We're relying on Foundry for everything, including managing all logins and automation clocks through their platform. I'm curious about the pros and cons of the two options. If I'm not mistaken, these additional screens and options were introduced after we initially set up the integrations with Acumatica.

Here is my understanding based on conversations with True Commerce and our Acumatica VAR:

The integration must be login in for Foundry to pull transactional data into Foundry from Acumatica.  If not, you will receive errors in Foundry.

When you log in to the integration, a token is set.  This token expires in 30 days in Acumatica 23 R1 (our current version).  We are upgrading to 24 R2, which removes the 30-day expiration on the token, which also removes the need to log back in to the integration every 30 days.  It’s more complicated than my explanation, but this is the high level.  

Thanks for sharing!