Why additional entity created by Abp Suite?? xxxWithNavigationProperties for Navigation Property #1381

8 Answer(s)

• 

  0

  abpVAndy created 3 years ago

  Any ideas? Need Help.

  Thx

  Save Cancel
• 

  0

  alper created 3 years ago

  Support Team Director

   ICollection<OrderLine> OrderLines 
   Product Product { get; set; }
   
  

  these are not navigation properties

  Save Cancel
• 

  0

  abpVAndy created 3 years ago

  Sorry is not Product. It is Order. Here is the whole class.

  public class OrderLine : FullAuditedEntity<Guid>, IMultiTenant
  {
      public const string DefaultSorting = "product.name asc";
  
      
      public virtual Guid? TenantId { get; set; }
      
      public virtual Guid OrderId { get; set; }
      
      public virtual Guid ProductId { get; set; }
      
      public virtual uint Count { get; set; }
      
      public virtual float StandardPrice { get; set; }
      
      public virtual float ActualPrice { get; set; }
  
      public virtual Order Order { get; set; }
  
      public virtual Product Product { get; set; }
  
      protected OrderLine()
      {
  
      }
  
      public OrderLine(Guid id)
      {
          Id = id;
      }
  
      public OrderLine(Guid id, Guid orderId, Guid productId, uint count, float standardPrice, float actualPrice, Guid? tenantId = null) : base(id)
      {
          TenantId = tenantId;
          OrderId = orderId;
          ProductId = productId;
          Count = count;
          StandardPrice = standardPrice;
          ActualPrice = actualPrice;
      }
  }
  

  Save Cancel
• 

  0

  abpVAndy created 3 years ago

  public class Order : FullAuditedAggregateRoot<Guid>, IMultiTenant
  { 
      public virtual ICollection<OrderLine> OrderLines { get; set; }
  }
  
  

  public class OrderLine : FullAuditedEntity<Guid>, IMultiTenant
  { 
      public virtual Order Order { get; set; }
  }
  

  Save Cancel
• 

  0

  abpVAndy created 3 years ago

  Here is the ABP Suite create addition class:

   public class BackCategoryWithNavigationProperties
      {
          public BackCategory BackCategory { get; set; }
          public BackCategoryBrother BackCategoryBrother { get; set; }
     }
  

  I have some confusion about it. Why create another class for the navigation relationship.

  Why Example easy-crm use property for the navigation relationship.

  Do you get my question? thx

  Save Cancel
• 

  0

  abpVAndy created 3 years ago

   ICollection<OrderLine> OrderLines  
   Product Product { get; set; } 
    
  

  these are not navigation properties

  Sorry is not Product. It is Order. Here is the whole class.

  public class Order : FullAuditedAggregateRoot<Guid>, IMultiTenant { public virtual ICollection<OrderLine> OrderLines { get; set; } }

  public class OrderLine : FullAuditedEntity<Guid>, IMultiTenant { public virtual Order Order { get; set; } }

  Save Cancel
• 

  0

  alper created 3 years ago

  Support Team Director

  because making property navigation is not best practise for a module. suite is designed to support both modules and app templates. but easy crm is not a module. if you are not working on a module template, you can change the final output of Suite to support ICollection<OtherEntity> OtherEntities

  Save Cancel
• 

  0

  abpVAndy created 3 years ago

  Thank you for your explanation. I will close this.

  Save Cancel