The user needs to pick one value and see the related values.
I need quite a few of these drop-downs in my app, so it's not appropriate to force the user to enter more complicated filtering criteria for each one. 100 items in the drop-down would not be too many for my app.
#Devexpress xpo code#
Yes, you can say that 630 is too many items to display in a drop-down, but this code is taking so long I suspect that the speed is proportional to the 49,000 and not to the 630. If you have a legacy accounts with us, you must validate your email address(es) before we can reset your unique account password. Is there another (simple) way to program the drop-downs and DetailView that runs much faster? An email has been sent if your submitted ID was found in the system. How can I make the associated values load faster? etc) and the goal right now is to make the end-user capable of saving changes submitted to these different controls by pressing a Save button. I took the time to sketch out the business case because I have two questions: devexpress xpo I am new to devexpress Im making a new WPF project with devexpress XPO, so far I have created some user controls (such as a Datagrid, a lookup edit. This is too long for users to wait for one of many drop-downs in the DetailView. The problem is that it takes 45 seconds to call theParentValue = this.DropDownOne. I don't think that persisting it will speed up the creation of the collection the first time, and after it's used to fill the drop-down, I don't need it, so I don't want to spend time storing it. I marked the DisplayedValues property as NonPersistent because it is only needed for the UI of the DetailVIew. I created a property in MyUI to return the collection of M圜hild objects for the selected value in the first drop-down. The user chooses MyParent1 in the first drop-down. The user chooses an item in one drop-down in the MyUI DetailView, and my code has to fill another drop-down with M圜hild objects. I have a DetailView for a class called MyUI.
There's a specific MyParent record called MyParent1.įor MyParent1, there are 630 M圜hild records. In M圜hild: // M圜hild (many) and MyParent (one)Īnd in MyParent: I have an association defined between MyParent and M圜hild in the standard way: XPO supports more than a dozen database management systems and implements a common high-level API. MyParent has a child class called M圜hild. eXpress Persistent Objects (XPO) is an Object-Relational Mapping (ORM) tool that handles all aspects of database creation and object persistence, allowing you to concentrate on your application's business logic. I have an XAF app with a parent class called MyParent. I am having a problem with the speed of accessing an association property with a large number of records.