What is the proper ABP implementation to add a repository that does not have an underlying entity? It is not based on an entity that maps to a table. For example, I have a dashboard that is running a complex query that joins many of my underlying tables, but I can't seem to register the repository in the EF Module. The add default repositories doesn't seem to pick up my repository, probably because it does not inherit efcorerepository. What is the right way to register it? Or, do I need to create an entity that does not map to an actual table?
Thanks, that worked for me.
I am trying to access the file descriptor service in javascript.
I am using this line, which was taken from the file management javascript file:
var fileDescriptorService = volo.fileManagement.files.fileDescriptor;
I get the following error:
Cannot read properties of undefined (reading 'files')
I don't understand why.
Ah... I can't wait to try that out and see how it works. Thanks again. I close those out.
You understand it correctly, but I should have added one important detail. I don't really care about update with those connections, I am fine with updating the way it has been implemented today. I really only see a need from a display and reporting side. Imagine a screen where you want to view the Product Details (from your sample), but you always want to know the product category (up a level), and what order line it used (up a level again), and the order id (up a level again). If you had navigation connected all the way down, you'd be able to do that with one database call. I know a custom sql call can pull that together, but I'd like to see ABP suite get a little more polished for even quicker development. In our complex cases we use ABP Suite to generate the base code, but then heavily modify it to support our need.
As for your link, I had not seen that yet. I also don't see the "Entty Type" selection in my version of ABP Suite. I am using V7.4.2. Why don't I see that?
Yes from ABP Suite. The current template generates a single level dto usually called ObjectWithNavigationProperties. This is great, but if that object has a list collection property with its own different navigation properties, it would be great to auto generate and connect to it as well. Maybe a toggle to specify how far deep to connect the objects navigation properties. I solved my immediate need by basically changing the ObjectWithNavigationProperties -> List<ChildObject> to ObjectWithNavigationProperties -> <ChildObjectWithNavigationProperties>. Abp suite is very powerful, but it just needs a few more items to make it so you don't need to code anything.
I have some nested many to many objects and I want to know what is the preferred way to show the nested items properties on the List page? ObjectA is the main object, it has the many to many edit tab to ObjectB. ObjectB has 1 to many navigation properties to ObjectC. On the edit modal for ObjectA, on ObjectBs list page (for edit and delete), I want to show more navigation properties on ObjectB. What is the proper way to do that? Ultimately, I want an object with full navigation properties all the way down from the starting object available to use on the List page. How should I implement that?
Maliming, You can find a sample project here: DELETED
Basically, using the many to many relationship to produce the UI child items is where to start. Take a look at ParentItems/EditModal.cshtml. Line 60 shows where I added the abp-tooltip. When defined like this it works. Now take a look at the editModal.js. Line 79 is where the child item gets dynamically added/rendered with the abp-tooltip. The item will show up in the UI, but the tool tip doesn't work.
Let me know if you are able to reproduce this. Thanks!
Using the abp-tooltip-left/top/bottom/right with dynamically added items does not work. You can use your many to many template and then add one of the tooltips to the java script to add it. The html doesn't render the tool tip. If you use the native bootstrap attributes data-bs-toggle, data-bs-placement, and data-bs-title, the tooltip works as expected.
Ah, I see. That worked. Thanks!