Sure, I created a Loom with the footage of the issue.
https://www.loom.com/share/0281cc2d84f24cc6950b803db9755ccf?sid=1661c041-1e0d-48b9-8cb4-9146716bc9c2
Dear EngincanV, I have also another issue with migrations. Sometimes the demo2 (with version 8.1.0.rc-1) doesn't apply any migrations at all, it's a weird bug because it happens (sometimes!!) when the project is created or when I create or update an already existing entity (It happens randomly). I will try to create a loom at the exact moment when It happens.
Hi, thanks for sharing the problem with a gif. Weirdly, I could not reproduce the entity deletion problem, and also could not reproduce the" entity names can not be the same with the namespace" problem.
I think it might be related to that you had a project name "Demo2" in the appsettings.json file of the ABP Suite and when you create a new project with the same name and by having the same entity "Book", it might get confused and gives the errors. So, can you check that you have a project with the name "Demo2" twice in the appsettings.json file?
What I acknowledge is that I'm able to edit the template to the point it would generate what I want, thanks to the present if branching a looping logic, but it feels like a really impractical solution to me. What I'm confused about the most are these variables:
%%main-edit-tab-opener%% %%razor-modal-fields-edit%% %%main-tab-closer%% %%razor-modal-navigation-connection-fields-editing%%
%%main-edit-tab-opener%% -> this only creates an opening tab for the TabPanel component (<TabPanel Name="..">) on the code side.%%razor-modal-fields-edit%% -> this corresponds to the related field components and you can edit the related txt files such as Field.Text.txt, Field.DateTime.txt, Frontend.Blazor.Page.Partials.Modal.Field.Numeric.txt, Frontend.Blazor.Page.Partials.Modal.Field.Bool.txt and Frontend.Blazor.Page.Partials.Modal.Field.Enum.txt%%main-tab-closer%% -> This is just for the closing tag of the TabPanel component (</TabPanel>)%%razor-modal-navigation-connection-fields-editing%% -> This is for navigation connections and use the field components again. (So, you can edit the related txt files like in the %%razor-modal-fields-edit%% placeholder)I will update the Editing Templates documentation.
Best Regards.
Hi, how can I reproduce it? I have created a project named "Demo2" like yours and filled in the entity metadata as in the screenshot that you shared, but could not reproduce it:
Hi, I created an article to show how to hide ABP related endpoints on Swagger UI by simply checking from the settings page. Your requirement is almost the same, so you can follow this article and update it according to your needs.
Also, please notice if you want to hide ABP-related endpoints on Swagger UI on development time, you can use the built-in option:
https://docs.abp.io/en/abp/latest/API/Swagger-Integration#hide-abp-endpoints-on-swagger-uiThanks, I used this method to hide endpoints before. But, we want t o manage this option dynamically. For example, if admin user select some module from UI, then we want to show it on swagger. Otherwise, users should not see this module's endpoints Is it possible?
Yes, it's possible. You need to create a custom document filter, check if the related permission is granted, or check if the role is admin for example, and then provide the related endpoints that you want to show by filtering endpoints.
But, as you would guess, this is a custom need and we are not providing a built-in option for that. So, you should create the document filter by yourself according to your needs.
Hi, I created an article to show how to hide ABP related endpoints on Swagger UI by simply checking from the settings page. Your requirement is almost the same, so you can follow this article and update it according to your needs.
Also, please notice if you want to hide ABP-related endpoints on Swagger UI on development time, you can use the built-in option: https://docs.abp.io/en/abp/latest/API/Swagger-Integration#hide-abp-endpoints-on-swagger-ui
From the last youtube podcast these are the most important features to us.
Bind to User Entities in ABP Suite Most important
We have implemented this one and it will be available with v8.1.
PDF export support Very important File/Image as a property type Uploads of multiple files on a record
For these two features, we have open internal issues but haven't prioritized them yet. File/Image as a property type feature might be implemented and released with v8.2.
Navigation Property: Current Behaviour: Only string properties are allowed!, UI pick type: 3 options New Behaviour: for non-string properties can we have 4th option for UI pick type: None and display property hidden.
I am not sure if it will be useful for general purpose or not.
We have an internal issue for allowing adding navigation property without a string display property and we aim to implement it with v8.2.
Hi, we have enhanced the flow to establish a relationship with entities of ABP modules in v8.1 and this problem will be fixed with v8.1. Thanks for reporting.
Regards.
Hi, this should have already been fixed. Please see the similar thread: https://support.abp.io/QA/Questions/6520/Error-when-adding-1-N-navigation-property-in-ABP-Suite-8
You probably need to make a clean uninstallation and then re-install ABP Suite to get the fixed version. Please follow steps mentioned at https://support.abp.io/QA/Questions/6520/Error-when-adding-1-N-navigation-property-in-ABP-Suite-8#answer-3a103316-d564-f4f0-b00b-a34fa1bc72d0
Hi, can you try to build your solution and share the build errors? Also, what is your exact ABP Version, v8.0.0 or different?
