Status Reason (statuscode) being set to a non-existent value from Power Pages Site

[aofosu]

When creating a record from power pages (enhanced model) this error code appears:

 

Something is trying to set the statuscode with this value 914550004 which is not part of the choice values of Status Reason. This issue began with choice values of other attributes being set to either 914550001 or 914550004 on the creation of a record in the account table. As a workaround, I added this value (914550004) in the Status Reason column which allows me to create a record from the portal side without issue, however, I cannot create any record in other tables as it's asking for the same status code value. This issue started after the enhanced mode was activated. Any clue what is going on?

[OliverRodrigues]

Hi, a few things you should check:

• is there any Metadata (Basic Form Metadata or Multistep Form Metadata) associated with that form/attribute with the option of "set value on save"? this might be trying to save the value to the status field
• is there any JS to that form setting the status field?
• is there any classic Workflow setting the status field?
• is there any Dataverse plug-in setting the status field?

[aofosu]

Thanks @OliverRodrigues,

my team and I tried all these steps and none but "set value on save" seems to be the issue. What we discovered was that when we add a metadata attribute on Power Pages to set a choice value on save (this could be in a different basic/multistep form that is not being utilized during data insertion), this issue comes back. It begins to affect all other choice elements having similar values. And at some point, the status code begins to ask for these set values as well that has not been set as part of the status code element. 

We tried creating both new global and local choice elements, they will work fine until metadata attributes are set to save a particular values during insertion. We tested this in a standard model and don't have these issues. The project manager would like to keep the enhanced model so I am trying to see if anyone has ever experience that and how they fixed it. 

We created a dummy insert form and added a metadata attribute to set the status code:

Now this form is just sitting dormant in Power Pages. I go back to insert a record using another form "[Insert] New Registration Form and this error comes back as for the status code which is not being altered in this registration form:

We also created a lookup field to set a value on save using the GUID. This was also affected. It would set that value in that column as long as it has been configured as metadata somewhere else. We then tested a simple text field and the behavior was the same as well when the Set Value On Save had been configured on a basic form or in multistep form.

[OliverRodrigues]

Thanks for the information, I am facing a very similar issue with the Set Value on Save with the Enhanced Data Model.

I reported my issue and Microsoft acknowledged the issue/confirmed that the fix would be coming soon. I am assuming your issue and mine are very much related. I will report this thread to Microsoft as well to see if they can give any update.

[aofosu]

Hi @OliverRodrigues,

How long ago did you report this MSFT? We are reporting this to MSFT as well, however, we would like to know if a solution or workaround is in place so we know to wait on them.

[OliverRodrigues · Accepted solution]

I reported the issue just before Christmas. 

The workaround in my case, and it might work for you as well, was to remove any "set value on save" from the Metadatas, and do that via JavaScript.

[aofosu]

This would mean writing custom JS code for each attribute we intend to set its value on save and paste them into the forms (in the custom JS sections). We will give it a try for now.

Another unrelated issue we have been facing is the redirect in a multistep form. It doesn't work in the enhanced data model. It throws an adx_webformstep with id 0000000-0000-0000-0000-000000000000 could not be found error. We may need to use JS to redirect the user onSubmit.

Thanks for your help!

[OliverRodrigues]

@aofosu if seems like we are working on the same project .. I also had the exact same error on the redirect😂

I reported that one too, but I am not sure when the fix is coming.

The metadata is scheduled for the end of January, and it will be Portal version 9.6.1.x

It would be great if the redirect fix is included, but I don't have confirmation yet

[aofosu]

@OliverRodrigues Yes it seems like. I think the enhanced data model needs some more time to be stable. 

So yesterday, our entire mspp got deleted (we don't know how so we opened a ticket with MSFT). Before that when changes were made to the header/footer templates in the root page (home) its deleted every custom code on that page. These are a few bugs we've discovered so far.

[OliverRodrigues]

😱 that sounds scary

overall I agree, I think it was not production ready when they released