Bug on Visual Designer

2 posts, 0 answers
  1. Daniel Bichuete
    Daniel Bichuete avatar
    9 posts
    Member since:
    Sep 2009

    Posted 10 Oct 2010 Link to this post


     I have detected one bug on you Visual Designer for OA. For reproducing it I'll explain a few steps and use some imaginary tables and domain.

     Well, let's assume a system that only log users in. You design the database first and create a Users table, a UserLogins table, a UserGroups table and a UserPermissions table. You setup the PK and FK.

     But as a mistake you setup UserLogins as many-to-one with Users, UserPermissions many-to-many with UserGroups and then you go and Add Domain Model on your project.

     This would generate the rlinq file and so on (let's assume using attribute on nested namespace on multiple files).

     Then you see your mistake and go on database an setup the FK for UserGroups and Users using a join table (many-to-many). After saving you go on Visual Designer, right-click and select Update from Database. Select the tables you updated and Finish.

     Visual Designer wont update (may be the way you want, but I think it should, but this is not yet the bug I mentioned, this is more a lack of feature that would be nice if implemented). Then if you delete the entities and try to add then again you would notice that associations now appears on Visual Designer (great!) but the IList collections arent there. If you look over the generated files the collections are there but not at the visual designer.

     For making this work I had to remove the whole domain, deleting the rlinq file and adding again. Then i displayed the correct visual entities and associations and collections.

    Best regards,

    Daniel Bichuete

  2. Petko_I
    Petko_I avatar
    184 posts

    Posted 12 Oct 2010 Link to this post

    Hello Daniel Bichuete,

    Thank you for your detailed explanation. We are aware of the visual glitch with navigation properties which are not displayed correctly when a remap is done. The generated code is fine because the OpenAccess meta model is correctly set up. So, you should not have problems working with your model and you should be able to use the navigation properties. The issue has actually been fixed and you will see the resolution in our next distribution.

    Do not hesitate to contact us again, should you notice anything troubling.

    All the best,
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top