Skip to main content
Answer

Is there a way to differentiate between a screen vs API action/creation

  • October 13, 2023
  • 4 replies
  • 52 views

Hi,

I am trying to build a report and an approval map for GL transactions, we want to exclude all created via API,

Is there a way to differentiate between a screen vs API action/creation? 

The only option I can think of right now is by API user I am wondering if there is a better dynamic way…?

Thank you  

Best answer by ChandraM

Hi @shlomo20 The other ways is to pass a Unique string from API transactions. in the Description fields as below. Or a similar solution.
 

 

4 replies

BenjaminCrisman
Acumatica Employee
Forum|alt.badge.img+4
  • Acumatica Support Team
  • October 13, 2023

@shlomo20 Unfortunately it looks like Created Through (indicating screenID) isn’t available in the mappings. The approval mappings only seem to see Created By and Created On, so unless the API user was a specific user, or somehow the process was using Admin user, it might be difficult to discern how the document was created.


Forum|alt.badge.img+8
  • Semi-Pro I
  • October 13, 2023

Hi @shlomo20 @BenjaminCrisman Having a Separate login user id for the API calls seems to be the feasible solution. 
Ensure not to share that account to anyone to avoid Journal Transaction entry with that user account.


Forum|alt.badge.img+8
  • Semi-Pro I
  • Answer
  • October 13, 2023

Hi @shlomo20 The other ways is to pass a Unique string from API transactions. in the Description fields as below. Or a similar solution.
 

 


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • October 14, 2023

Hi @shlomo20  In addition to Chandra’s comment, I would recommend implementing a flagging mechanism. Upon document creation, the make system automatically mark this flag as 'checked.' This strategic approach will significantly enhance our ability to differentiate documents and effortlessly execute subsequent functionalities.