Activities of "okains"

Ah yes, I was using the AccountResource instead of my SITOResource. I should have seen that! Thanks for pointing that out, ill close this now.

OK that will work for now, can you let me know how to track this so I know when it is fixed?

And since this is a bug can you refund my question credit?

Thanks,

Karim

OK perfect, thanks.

OK so yes Non Nullable Enums work with the Blazorise Grid. I tried changing the Enum to Non Nullable but when I regenerated with ABPSuite it gave me some bad code, maybe you can take a look at this also ( screenshot below ). So updating to Non Nullable isn't an option for me.

Removing the Nullable Enum field from the DataGrid is the workaround for now. Please let me know when you think this issue can / will be fixed so that I can plan accordingly.

Also since this is a bug can you please credit me back this support ticket?

Thanks,

Karim

This is still throwing the same error, screenshot below. I didn't change any code, just generated straight from ABP Suite, exactly as discussed. Added a Country as shown, with Asia selected, and getting the same error message.

I have tested this in Chrome, Firefox, Edge, Brave browsers, all the same error.

The DataGrid field is generated as nullable right from ABP Suite:

          <DataGridColumn TItem="CountryDto"
                  Field="PhoneCountryCode"
                  Caption="@L["PhoneCountryCode"]">
          </DataGridColumn>

          <DataGridColumn TItem="CountryDto"
                  Field="WorldRegion?"
                  Caption="@L["WorldRegion"]">
                <DisplayTemplate>
                    @L[$"Enum:WorldRegion.{context.WorldRegion?.ToString("d")}"]
                </DisplayTemplate>
          </DataGridColumn>
          

Hi Anjali,

Upgrading to 2.4.1 and bundle / clear cache etc worked. Thanks for your help!

Karim

Even if this doesn't help you try to update Leptonx version.

Looks up to date here, version 2.40

Hi Anjali,

OK I am following these steps exactly as above but still getting the same result.

First of all to confirm, when you refer to the Host project, I am assuming that you mean the HttpApi.Host project? In my case ESv2.HttpApi.Host ( screenshot below ) ?

Second, after a dotnet clean / restore if I run abp bundle on the Blazor project I get an error as noted in a previous message on this chain. So I need to build the Blazor project first, then I can run abp bundle without any issues.

Other than that I am doing everything exactly as stated and getting the same error. The only other thing that I can think of that I have not used before is the PWA support, could that have anything to do with this?

Hi Anjali,

I have followed your previous steps multiple times, they do not resolve the problem. I am sure that we are missing a step here.

This is a Blazor WASM project, I don't see a node_modules folder. I did run yarn and npm but they didn't do much. The repeated the previous steps, and got the same result.

You mentioned earlier that you have released a patch release to fix this:

We have released a patch release for LeptonXToolBar issue.

You haven't told me how to get this patch release, is this the step that we are missing here? I see that you are working on a 7.4 Patch release, is the actual fix for this in there?

Thanks,

Karim

Hi Anjali,

Any update on this? I just saw the 7.4-patch Milestone but I can't seem to find this issue documented there. If there is another way to fix this, or if I am missing a step with your instructions above please let me know, I need to demo this soon and this bug is preventing me from doing so.

Thanks,

Karim