Unexpected result type of schema evaluation when trying to poulate new CDS table with Data from on premise SQL DB

(3) Share

Report

Posted on by jamesbetteridge

Hi,

BACKGROUND

I am pretty new to CDS. I have built a number of powerapps using Sharepoint lists as the datasource but recently built an powerapp that references data in an onprem SQL database table. Everything works but data load times are poor.

I am trying to setup a copy of the SQL table in CDS, initially for testing but then later as a live environment with changes in the onprem SQL table updating the CDS table automatically.

ISSUE

I am failing at step one at the moment. I can go into either "Data" or "Dataflows" from the powerapps portal, I can create a table in CDS (just has one column at the moment) and I can follow through some of the process i.e I can see the DB i want to connect to and can select the required table as well as select "Transform Data" and select all columns. When I click "Next", after about 20 seconds, I get the following error:

Unexpected result type of schema evaluation. Expected: "Table". Actual: "Exception".

I have searched the internet for this error but cannot find anything useful. I would be eternally grateful if anyone can shed any light on why I might be getting this error and more importantly, how to get past it!

Kind Regards

James

Categories:

Building Power Apps

I have the same question (0)

All responses (12)

Answers (0)

Javier Gallego on at

Like (1)

Report

Hi jamesbetteridge,

I would like to suggest that you raise a support ticket by clicking the 'Create support ticket' button on the following page. That way, you'll have something that's a bit more traceable and you might receive a quicker response.

https://powerapps.microsoft.com/en-us/support/

We will need to check more details about the issue.

Thanks,

Javier

Was this reply helpful? Yes No
wardporterfield 4 on at

Like (1)

Report

I am BY NO MEANS an expert as I've only been playing around with PowerApps for a couple months, but I was getting the same error today. Decided to try to just add a record manually and got an error saying I didn't have permissions to the form (which I know I do). If I refreshed the form, it worked. So I logged out of Power Apps completely, and then tried reloading the data through the wizard and it worked fine. tl;dr log out, log back in and try it again.

Was this reply helpful? Yes No
JandroH 5 on at

Like (0)

Report

Hi
I am getting the same error, @jamesbetteridge did you get any clue about the error?
thks in advance

Was this reply helpful? Yes No
jamesbetteridge 50 on at

Like (0)

Report

Hi All, Unfortunately I haven't had opportunity to follow this up yet but will try to do so by the end of this week. I will let you know if I achieve any success.

Was this reply helpful? Yes No
notj 782 on at

Like (0)

Report

@jamesbetteridge how'd it go?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Any update to this? I am getting it too.

Was this reply helpful? Yes No
notj 782 on at

Like (0)

Report

@Anonymous I was trying to bring a list with an InfoPath form into my table. I had to be particular about the fields I brought in, as some of those fields were being treated as their own tables.

Basically, my suggestion is try doing this with just one single text field and see if it works. This should help determine if one of your fields is causing the problem or not.

Was this reply helpful? Yes No
Roma Gupta 167 on at

Like (0)

Report

Hi All, I had this issue this week with just one table selected. In my case, there were many columns with values as [Record]. I was getting the same error after transform.
I figured it was mostly lookup columns. I had to remove those columns & the error was no longer appearing.

Hope this helps.

Was this reply helpful? Yes No
jamesbetteridge 50 on at

Like (2)

Report

So sorry for the reaally long wait for a reply on this one. It hasn't been a priority and other projects have meant that this one has taken a while to resolve. With thanks to Microsoft Support's Adebiyi Ebenezer, this is now working!

Embarassingly, the problem was with an extremely outdated on-prem gateway. The gateway software had last been updated two years ago and so updating this to the latest version solved the issue. Adebiyi originally walked me through a number of steps, including adding a powerapps per user trial license (as it appeared to be licensing issue at first) but ultimately nothing worked until we stumbled acorss the gateway software version being so old.

Apparently new versions are released monthly (more often than not) and so it is imperative that it is kept up to date.

Was this reply helpful? Yes No
crisfervil 126 on at

Like (0)

Report

I've got the same error today in DataFlows. It turns out my source table was empty, and adding a new record solved the problem.

Was this reply helpful? Yes No