Activities of "EngincanV"

Hi, yes you can use the custom code support to add an entity-action to the data table directly. You can apply the following steps:

1-) Edit Frontend.Mvc.Page.index.js.txt template and add custom-code block placeholder:

                           //<suite-custom-code-block-10>
                              //your custom code goes here...
                          //</suite-custom-code-block-10>

2-) Regenerate the same entity, after you do that the placeholder will be added for the related entity, and you can update the content in the placeholder for the related index.js file:

                           //<suite-custom-code-block-10>
                           ,{
                                text: l("ClickHere"),
                                action: function (data) {
                                    //define what should happen when to the action clicked
                                }
                            },
                          //</suite-custom-code-block-10>

3-) Then in the next code generations, ABP Suite will respect your change, and will not override the specified section.

For further info please refer to the documentation: https://abp.io/docs/latest/suite/customizing-the-generated-code#adding-new-custom-hook-points-changing-their-places-1

<suite-custom-code-block-10> is just an example placeholder, you can use any number, however, please note that the number should be used only once per page.

Hi, indeed there is a problem as you stated. But this is by design for now. I will create an internal issue for that because I agree that we should also reflect the impersonation on the auth server side.

Thanks for reporting. Regards.

Hi @EngincanV ,
why did you close the thread about abp 8.3?

https://abp.io/support/questions/7844/Bugs--Issues-v83x

Thanks

Hi, it was by mistake. Thanks for reminding me. I've reopened it.

yes! worked

Glad to hear that. Probably it was a temporary problem due to your projevlct and suute integration. Closing the question since your problem is resolved.

Feel free to reopen it if it occurs again. Best regards.

Hi, this is indeed a very strange bug. Can you remove your solution from ABP Suite, then clean&build your solution and try to add the solution again and regenerate CRUD pages?

Indeed there is a problem as you stated. I will create an internal issue for this problem.

However, for a quick workaround you can apply the following instructions:

1-) Open the appsettings.json file (it's under the %%user-profile%%.abp\suite) and manually fix the following parts in the solution section:

Change UiFramework to 7, set the BlazorWebAppProjectDirectory as your project directory:

      //...
      
      "Name": "<YourMicroserviceName>",
      "UiFramework": 7,
      
      //...
      
      "BlazorWebAppProjectDirectory": "<your-directory-structure>\\apps\\blazor",  
      
      "UiFrameworkName": "BlazorWebApp"

This will fix the code generation path but the menu item creation still be problematic and give errors. So for now, I suggest you to generate everything except the UI, and wait for the next patch. In the next version, once we fix this problem, you can regenerate it with the UI.

Sorry for the trouble. Regards.

Hi Engincan, thank you for your return.

As I have a limited amount of credits in my licensing, considering this is a Bug and will be fixed, please reset this credit Issue counting on my account. Now I have no more credit but when you return me this credit I will be able to open a new ticket in the future.

Sure, I have refunded your ticket and closing the question.

Thanks for your understanding. Regards.

Hi again, we reproduced the problem as you stated and created an internal issue (with number 2626) and will fix the problem as soon as possible.

Best Regards.

Hi, as far as I understand, you did not generate-proxy after Suite code generation, right?

You should generate C# proxies, as described in the Microservice Tutorial, here is the link for the related section: https://abp.io/docs/latest/tutorials/microservice/part-03#generating-the-ui-proxy

Please, follow this section and let me know if it's fixed. Best regards.

Thank You. So looking at it I am currently stuck and can't proceed until there is a fix. Please let me know how to proceed in the absence of a fix. If Proxies can't be created then how do we proceed with building UI

Actually there is no blocking problem. You can use the following flow for now ( I assume that you already have an microservice solution ):

1-) Create a new microservice from ABP Studio:

2-) Open the ABP Suite, and generate CRUD pages with your configuration for this microservice:

I created a Category entity with Name as its only property for demonstration.

3-) After generating CRUD pages for a service (CatalogService), you can run all of the runnable projects. Once all of them are up, you can send a request to the CatalogService's endpoint (/api/abp/api-definition) and you'll see the Catalog in the JSON response:

Run all projects:

CatalogService's endpoint (/api/abp/api-definition)

Response of the endpoint (catalog section)

4-) Then if needed run the generate-proxy command (before that you should change the default API from environment.ts file)

Please note that, normally you don't need to manually run the generate-proxy, because ABP Suite already should be doing it for you in the angular code generation. However, if there is a problem you can follow this step and manually generate-proxies.

Change the URL from adminstrationService url's to CatalogService's URL, for only proxy generation, then please don't forget to revert it)

    default: {
      // url: 'http://localhost:44316', -> administration service
      url: "http://localhost:44334", // -> catalog service
      rootNamespace: 'Issue8665',
    },

Generate proxies:

abp generate-proxy -t ng -m catalog