I’ve been working on a small project using the UD101 form on an off over the last week or so. Everything is looking good, but I have come across some unusual behavior and need some guidance.
When I started the build I used an ultracombo against the key1 field and was able to load project ids from a baq, which worked well, or so I thought. When creating a new UD101 record it works nice and fast, however if you subsequently leave the form, reopen it, and run a search, and select the record you just created, or others, all of the fields populate apart form the combo. I know there is data exists as I just left the key1 field on the form and see it getting populated. I sure I must not be setting a property correctly, but for the life of me I can’t work out what it is.
I did a bit of research and discovered that the epicombo is really the preferred method, and on testing the epi combo populates with the projectid from the search, but actually using the combo to select data is painfully slow.
With the epicombo, I am using the Project BO with a filter of ActiveProject = 1 and Shortchar02 = ‘DEV’ (we categorize projects with shortchar02).
I have also tried debugging with VS2010, but have not had a great deal of success on that front either.
Normally for combos I use Ultracombo for lists that are tied to the form
item and EpiCombo for lists made in User Codes. We were able to drop many
UD tables by using lists of User Codes codes and it’s pretty easy to setup
a updatable dashboard for the users of those departments to manage their
own lists as well.
Rookie mistake…Looks like I needed to initialize the Ultracombo properly. Originally had the initialization of the BAQ in the before drop down event. Put it into the Form load and that resolved the issue.
That’s a great tip Randy. I too use EpiCombos for UserCodes, but had not considered creating an updatable dashboard for self maintenance. I like that a lot.
@josecgomez.sixs…Admins …Can we stick that in a Really Great Idea Category Please
Just make a post with the dashboard attached and the advice to go with it. We’re trying to move away from generic repositories with the search capabilities.
