Interface table and functionality

[Khanna Ji]

Hi Friends,

I have a requirement from a client to build a common functionality to store the data of all integrations and must be processed via a common table.

It will show Incoming or outgoing data, request body, response body, http status, error messages etc. I suggesting we can have one table for outgoing data but for incoming data we should use Inbound Web services based on the requirement of the interface.

Can you guys share your expert opiniton or update set if somebody has already build something like this? Generic tables for any time of interface/integrations which can be used for troubleshooting.

[Ankur Bawiskar]

@Khanna Ji 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Khanna Ji 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Khanna Ji 

I believe I shared a working solution for your question.

Did you get a chance to review?

Members have invested their time and efforts in helping you.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Khanna Ji 

Hope you are doing good.

Did my reply answer your question?

💡 If my response helped, please mark it as correct ✔️ and close the thread 🔒 — this helps future readers find the solution faster! 🙏