Dataverse Model Driven App Command Bar Power FX Button - Error today -Cannot read properties of null (reading 'identifier')

[sharonsammy123]

I have a command bar button on a main form using power fx formula. It clones a record. It was working fine until today (it looks like Microsoft did a copilot update??). It is now not working and I get the following error:

Error:  Cannot read properties of null (reading 'identifier')

I have removed and re-added the datasource in the DefaultCommandLibrary (canvas app) but it has not helped.  Is anyone having a similar problem and any ideas on how to solve?

Edit - here is my power fx formula - it was working fine until today????

If(
Confirm(
"Are you sure you want to clone this order?",
{
Title: "CLONE AN ORDER",
ConfirmButton: "Yes",
CancelButton: "No"
}
),
// If user clicks "Yes"
With(
{
NewOrder: Patch(
Orders,
Defaults(Orders),
{
'Order Type':Self.Selected.Item.'Order Type',
'Plan No':Self.Selected.Item.'Plan No',
Portfolio:Self.Selected.Item.Portfolio,
'Lot No':Self.Selected.Item.'Lot No',
'Account Code':Self.Selected.Item.'Account Code',
'Issue No':Self.Selected.Item.'Issue No',
'Contractor No':Self.Selected.Item.'Contractor No',
Description:Self.Selected.Item.Description,
'Site Contact Lot':Self.Selected.Item.'Site Contact Lot',
'Start Date':Now(),
Report:Self.Selected.Item.Report,
'Internal Notes':"Cloned from " & Self.Selected.Item.'Order No' & ". Please update before sending"
}
)
},
Navigate(NewOrder);
Notify("Cloning process completed. Please update before sending.")
),
// If user clicks "No"
Notify("Cloning process aborted.")
)

[sharonsammy123]

Microsoft have acknowledged my support request and have reached out to me for more details.  

[anosiara]

We have experienced the same problem with one of our customers beginning this week. I assume Microsoft has pushed through an update over the weekend. Command Bar buttons with PowerFX on select are causing the problem. With tedious debugging by commenting out code, you can find the dataverse reference that is causing the problem. When you find it, it makes no sense why this reference is no longer working but others for the same record are fine. It was always a particular "Self.Selected.Item.xxxx" reference causing the problem, but not all of them. We triple checked, and those references should be fine.

The PowerFX fomula helper thinks the reference is fine and prompts you to use it. You dont get any errors when you define the formula.

No code is executed when you get the error, PowerApps just decides in advance that reference wont work. eg. If your first line of the formula is a plain text Confirm statement (no references), it does not get executed.

I think Microsoft has introduced a bug when parsing the formula at runtime.

We had to workaround for now by creating the record with hardcoded values and then used a synchronous workflow on create to fix it up.

[devcr]

I am also having the same issue all of a sudden.

I wonder when MS will fix it.  I can put a support request in also.

[HKNeo]

I've done the same yesterday, and working with MS support. So far the fixes they have tried (removing powerFX code and adding it back, and also updating the authoring version to the latest) but none has helped.

i have a feeling it is related to retrieving the value of a related item in powerfx.  If i retrieve fields of the same table with self.selected.items, it works, but if i take a related field, it gives this error since monday (has been working fine ever before)

[anosiara]

We have experienced the same problem with one of our customers beginning this week. I assume Microsoft has pushed through an update over the weekend. Command Bar buttons with PowerFX on select are causing the problem. With tedious debugging by commenting out code, you can find the dataverse reference that is causing the problem. When you find it, it makes no sense why this reference is no longer working but others for the same record are fine. It was always a particular "Self.Selected.Item.xxxx" reference causing the problem, but not all of them. We triple checked, and those references should be fine.

The PowerFX fomula helper thinks the reference is fine and prompts you to use it. You dont get any errors when you define the formula.

No code is executed when you get the error, PowerApps just decides in advance that reference wont work. eg. If your first line of the formula is a plain text Confirm statement (no references), it does not get executed.

I think Microsoft has introduced a bug when parsing the formula at runtime.

We had to workaround for now by creating the record with hardcoded values and then used a synchronous workflow on create to fix it up.

[Veeks01]

Still getting issues myself too - can someone provide a link with where I can raise a support ticket to help bring Microsoft's attention to this? Having issues finding where exactly to raise one. Many thanks

[Sam7799]

I started having the same issues here as of Monday - even a basic lookup to related field not working and showing "Cannot read properties of null (reading 'identifier')".

My basic code on a button is : 

Launch(Self.Selected.Item.'Engaging Body'.'Portal URL')

It seems its the reference to a related field from one entity to another. Other codes with this lookup in also are not working as of Monday. Seems like a bug!

[MarkPP]

You will need to raise a support ticket from the Power Platform Admin Centre. You will need to ensure you have access to do this or speak to your admin to raise one on your behalf.

Microsoft have said there investigating it as a high priority as they have many customers with the same issue and will let me know when they have an update.

[sharonsammy123]

Hi all, just an update. I still have the error. Microsoft have reached out. They have also listed the item as a known issue on their support page. There post is as follows;

Problem

After publishing using PowerFX commanding, and an FX button is clicked, an error message with "Cannot read properties of null (reading 'identifier')" shows up

Workaround

There is no mitigation steps at this time. Please hold on until we establish mitigation steps.

[sharonsammy123]

Hi all, good news, just noticed this update on power apps "known issues" support page - 

Problem

After publishing using PowerFX commanding, and an FX button is clicked, an error message with "Cannot read properties of null (reading 'identifier')" shows up

Workaround

We have rolled out a fix that will start deploying on 2024-05-03