There was a problem saving your changes. The data source may be invalid. - when adding record in a table which has trigger

[Anonymous]

Good day,

I have added a trigger on insert/update for two fields and now I am getting the above error when adding a record in the table from the Power Apps form.  Is there any way to make the power apps form work when having a trigger on the table?

Thank you.

[v-yutliu-msft]

Hi @Anonymous ,

Could you show me your formulas and screenshoots?

The reason of  "The data source may be invalid" may be many possibilities.

Please check whether you have connect with your data source successfully.

Try to refresh your data source.

You could check it here:

Best regards,

Community Support Team _ Phoebe Liu

[Anonymous]

Hello @v-yutliu-msft ,

From what I read in an older post, Power Apps SQL Connector does not allow triggers. The data connection is successful but I cannot save the form. I have attached print screens with the data connections and the error message. 

If I remove the trigger everything works fine.  I have tried obtaining the same by using  functions and making the fields computed, but I also get an error ( attached) . Is there any limitation  when having computed columns in the table? ( the computed columns are calculated based on SQL join)

Thank you,

[Anonymous]

I am also adding the print screen with the error message which appears in the Save Form.

[v-yutliu-msft]

Hi @Anonymous ,

I'm afraid it''s not supported to use SQL calculated field in PowerApps currently.

Some one has posted a similar idea, you could vote for him:

https://powerusers.microsoft.com/t5/PowerApps-Ideas/SQL-Output-Clause-error-on-calculated-column/idi-p/41844

I suggest you do calculation inside PowerApps, here's a doc about it for your reference:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/define-calculated-fields

Best regards,

Community Support Team _ Phoebe Liu

[Anonymous]

Thank you for your answer, @v-yutliu-msft . I was thinking that maybe this could be a solution for the triggers :), but it seems it isn't.

[Anonymous]

@v-yutliu-msft the curious thing about this is that in the SQL table I have another computed column, which has the formula Column1  AS (CONVERT([nvarchar](50),[Column2])) and this column raises no issues when saving data. Could there be an issue only with the functions?

[v-yutliu-msft]

Hi @Anonymous ,

Please check the doc the last part :

(You should be aware of certain conditions and limitations when working with calculated fields:)

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/define-calculated-fields

The formula works may not beyond the limits.

Best regards,

Community Support Team _ Phoebe Liu