Unanswered

Teams Dataverse Table changes over time

(0) Share

Report

Posted on by PaulBI

I originally thought this was a PowerApp issue itself but I think it has something to do with how PowerApp is connecting to the Team's Environment. With that new information, hopefully this is the right group to post this to. I had the below except instead of Update table it was connect to a project activities table. It kept giving an error in the Patch that this column was not available in this context. I created a new teams table (Updates) and connected to that and all errors went away and it worked perfects. That was from Wednesday to today. I didn't change anything in the Teams table or in the app and now it is giving the same error for the Updates table that it did for the Project Activities table. Based on this I can only assume something changed in how PowerApps connected to the Teams environment. I've tried disconnecting and reconnecting the datasource and refresh the datasource and none of those will work. The only solution I have is to create a new table and reconnect to it every 2 days which is not a sustainable solution. Any ideas what would be change in that 2-3 day range in how the datasource is connected?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (1)

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @PaulBI,

What's the full error message you get? Also would it be possible to share the full expression, it's cutting off at the end? I don't think it has to do with the table itself, but perhaps the authentication? Ensure you connect with an account that doesn't have MFA.

Thanks!

Was this reply helpful? Yes No
PaulBI 91 on at

Like (0)

Report
Below is a screenshot of the actual error. If I isolate on just the patch it is definitely originating there. the full code is also below. Originally when I thought this was an issue with the code I originally posted in the Building Power Apps group, but when it worked I marked that as solved but since it randomly started again but with a totally different table I opened a new thread in the Dataverse group because I'm leaning towards something with the connection. I'm not on MFA and the error stopped originally (when I created the new table) and worked for multiple users and randomly started today also for multiple users at the same time.
ForAll(galWorkItems_1.AllItems, //**** Task Title If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).Name <> lblWorkItemTitle_1.Text, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Task title changed to: " & lblWorkItemTitle_1.Text , 100 ), updatedescription: "Task title changed to: " & ": " & lblWorkItemTitle_1.Text, Code:"8"})); //**** Task Description If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).Description <> lblWorkItemDescription_1.Text, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Task description changed to: " & lblWorkItemDescription_1.Text , 100 ), updatedescription: "Task description changed to: " & lblWorkItemDescription_1.Text, Code:"9"})); //**** Task Category If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).Category.Name <> lblWorkItemCategory_1.Selected.Name, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Category changed to " & lblWorkItemCategory_1.Selected.Name , 100 ), updatedescription: "Category changed to " & lblWorkItemCategory_1.Selected.Name, Code:"5"})); //**** Task Milestone If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).Milestone.Name <> lblWorkItemMilestone_1.Selected.Name, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Milestone updated to " & lblWorkItemMilestone_1.Selected.Name , 100 ), updatedescription: "Milestone updated to " & lblWorkItemMilestone_1.Selected.Name, Code:"3"})); //**** Task Priority If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).Priority.Name <> lblWorkItemPriority_1.Selected.Name, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Priority updated to " & lblWorkItemPriority_1.Selected.Name , 100 ), updatedescription: "Priority updated to " & lblWorkItemPriority_1.Selected.Name, Code:"4"})); //**** Task Assignee If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).'Team Member'.Name <> lblWorkItemAssignedTo_1.Selected.Name, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Work item assigned to " & lblWorkItemAssignedTo_1.Selected.Name , 100 ), updatedescription: "Work item assigned to " & lblWorkItemAssignedTo_1.Selected.Name, Code:"2"})); //**** Task ETA If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).ETA <> lblWorkItemETA_1.Value, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Target date changed to " & lblWorkItemETA_1.Value , 100 ), updatedescription: "Target date changed to " & lblWorkItemETA_1.Value, Code:"7"})); //**** Task Status If(LookUp('Project Work Items',Text(msft_projectworkitemid)=Label1.Text).'Work Item Status'.Name <> lblWorkItemStatus_1.Selected.Name, Patch(Updates,Defaults(Updates),{ Projectupdated:gblProject, updatedworkitem: LookUp( 'Project Work Items', Text(msft_projectworkitemid) = Label1.Text ), Name: Left( "Status Changed to " & lblWorkItemStatus_1.Selected.Name & ": " & lblWorkItemTitle_1.Text , 100 ), updatedescription: "Status Changed to " & lblWorkItemStatus_1.Selected.Name & ": " & lblWorkItemTitle_1.Text, Code:"6"})) )

Was this reply helpful? Yes No
PaulBI 91 on at

Like (0)

Report

Sorry, wasn't hovered directly over the defaults portion so the whole error message isn't there. Below is the full picture of the fault:

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
And to isolate, which exact Patch statement is causing the error? Can you also ensure the following:

Import data source experience is on: https://powerapps.microsoft.com/blog/improved-data-source-selection-and-common-data-service-views/

Use the intellisense, display labels in the Patch statements instead of the physical names (e.g. msft_projectworkitemid).

msft_projectworkitemid is a GUID in the Dataverse so not sure why converting to text and comparing with label. It would also be false... (E.g. Text(msft_projectworkitemid)=Label1.Text)

Thanks!

Was this reply helpful? Yes No
PaulBI 91 on at

Like (0)

Report
I verified the Import Data Source experience was on. I went and simplified the original statement down to just the patch inside the forall to isolate down to that driving the error. So now my statement is the below simplified statement but showing all the same errors around column not accessible that I pasted above. One really strange thing I noticed is that even though I am selecting this Table from the suggestions, it doesn't seem to recognize is as a table (the font stays black instead of teal). If I replace it with another table (other than this one and the original one that I created the Updates one to replace because it was doing the same thing) it recognizes it and doesn't throw any errors... The other thing that I just noticed is when I look at the Updates table it says it was last updated 3 months ago. This table didn't exist until last week. The original table I was using Updates to replace doesn't seem to have the same issue with when modified so that could be a red herring. The other strange thing that I just noticed is that last week when the statements were working, in the updates table the project and work items were updating (I specifically was reviewing and comparing the _msft_workitem_id_value and _msft_project_id_value columns) now they are totally blank, even rows from last week when it was working. Which leads me to something changed/impacted those columns which is also causing issues with patching to it last week when it stopped working randomly. Taking a look at the relationships in the Teams Table now and working if I converted everything from a lookup to just plain text and create the relationships later if that will resolve this. Trying it now, but I'll take any other advice anyone has too. Hopefully everything above makes sense, but let me know if I can clarify anything.

ForAll(galWorkItems_1.AllItems, Patch(Updates,Defaults(Updates),{Name:Label1.Text}))

Was this reply helpful? Yes No
Verified answer

PaulBI 91 on at

Like (0)

Report

Ok so I created a 3rd brand new Teams Table but this time only have straight text columns that will be writing the ids instead of lookups and am now referencing that table successfully in the original statement. I think my only concern is that when I created my second table (the duplicate of the first which had lookups) it was working for 2 days before it stopped. I'll have to keep watching in the meantime and if anyone has any ideas what's causing this so I can confirm it will stop this iteration from not working or fix it pre-emptively I would appreciate it.

Thanks

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi Paul, apologies for my late reply. That is weird and other users also reported that issue. So good thing is that it's not related to the lookups but something after a couple days. Have you tried opening a ticket at Microsoft: https://admin.powerplatform.microsoft.com/support? They will be able to provide additional details with their telemetry and internal logs. Keep us posted...

Was this reply helpful? Yes No