Problem with 1:1 subobject in business objects datasource

Comments

• AlexTZ

  June 2009 edited 7:12AM

  Hello Marco,
  
  Thanks for the test project.
  Due to some reason, XAF returns the Address.Country property type descriptor as IEnumerable. I think it is internal logic of XAF. But I cannot distinguish between 1:1 properties and lists. I think I will add another event that you will use to return correct property metadata.
  
  Regarding the GUID: it is possible now to get a column value of Guid type and convert it to string:
  [Table.GuidColumn].ToString()
• AlexTZ

  June 2009 edited 7:12AM

  I do some investigations and here is a result:
  When FR asks XAF to get property descriptors for the particular object, XAF returns own property descriptors, instead of real properties of your object. Looks like XAF descriptors are used to support internal logic. For example, if you want Address.Country property, you will get XAF descriptor telling you that it is XPCollection property (instead of property of "Country" type)! That's why you see Country element in the Data tree as a datasource, but in "real word" it is just a nested property.
  
  To solve this problem, I corrected the FilterProperties event handler so it will be able to replace the property descriptor returned by XAF with real property of your object. The fixed version will be available in 7 hours. Here is a code of new event handler:

          void ReportSettings_FilterBusinessObjectProperties(object sender, FilterPropertiesEventArgs e)
          {
              if (e.Property.Name.Contains("!") || e.Property.Name=="This" || e.Property.Name=="Oid")
              {
                  e.Skip = true;
              }
              if (e.Property.PropertyType == typeof(XPCollection))
              {
                Type componentType = ListBindingHelper.GetListItemType(sender);
                PropertyInfo propInfo = componentType.GetProperty(e.Property.Name);
                e.Property = TypeDescriptor.CreateProperty(
                  componentType, 
                  e.Property.Name, 
                  propInfo.PropertyType, 
                  null);
              }
          }
  
• MarcoTheFirst

  June 2009 edited 7:12AM

  Hi Alex!
  
  Thank you so much for looking into this and extending the FilterProperty event! I'm looking forward to the update.
  
  It's really strange what they do in XAF... I hope this is the last weird thing I had to bother you with for some time. :-)
  
  Regards
  
  Marco
• MarcoTheFirst

  July 2009 edited 7:12AM

  Alex, just to let you know: Your changes fixed all the problems I had! Thanks again! I'll keep you updated on how my XAF module comes along. If you're interested we could offer a "package deal" to developers using XAF who want to switch to FastReport.
  
  Regards
  
  Marco