Table Created in Visual Studio not appearing in Power Automate

(0) Share

Report

Posted on by Community Member

Hello Experts , I am not sure how relevant this question is for this forum but if anybody has any experience with similar issue please suggest.

I have created on table name "BG_ActivityRecorder" from VS and this table is appearing in SQL side but when i am connecting this table through Power Automate this table doesn't match and PA gives an error. that mentioned table name is not matching.\

I have checked access in SQL side , there is nothing wrong there shall i check something on VS side or any table properties.? Please advise

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Sachin Gupta,

What connector are you using in PA? As far as know you can connect to tables directly outside F&O and you need to create an oData public entity for the table.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Sergei, Thanks for looking into this issue. I am using SQL On premise Connecter. yes you are right we no need to create any oData Public entity.

Actually i am able to fetch other table (UserCreated , System created) but only this table is having some issue. This is the error comes when i try to load in PA.

i also tried full DB sync but but still the same issue

Was this reply helpful? Yes No
Suggested answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Sachin Gupta,

It's not a good idea to insert records directly to DB and bypass x++ logic:

1. You bypass core F&O logic like RecId allocation

2. You bypass security set up

Personally, I haven't used SQL connector, but I assume the error is related to the primary key. Have you compared the primary key for tables where the connector is working and the primary key on your table? Maybe the surrogate key is the issue.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Hello Sergei , I am completely agree with you its not good to write back in DB without X++ logic and bypass security setup. but this is just to test something on Dev server,

My issue has been solved , i have deleted and recreated the table also this time i have entered the table name in Caps which is default creation of table in d365. now i can load table in Power Automate.

Thank you for your valuable suggestion Sergei, have a great day

Was this reply helpful? Yes No
André Arnaud de Cal... 300,915 Super User 2025 Season 2 on at

Like (0)

Report

Hi Sachin,

I'm glad you solved your issue. Note that it is not best recommended to test directly on a production environment.

I have marked your answer to close the question.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hello Andre, Thank you so much for your kind response actually by mistake i have mentioned Production server its Dev server , i just corrected it.

Was this reply helpful? Yes No