I've changed some property names to friendly names using custom code option in Business Object Mapper.

(Plus override GetCustomBindablePropertyDescriptors for these fields)

I've noticed that when this object was bind to a Devexpress Grid with business binding source, these properties were not seen in Devexpress Grid.

I've tested for Devexpress (Wrapped) Textbox. These fields were listed in the BindingField list of the textbox.

What is missing ?

I've checked "Use Custom Code" and No other option is selected in Business Object Mapper. Simply, I want to change the property names to more friendly names. For a field, I've got the generated code for a property, Pasted into Field's custom code section, Changed the property name. And Within my class (CustomersBase) overriden the method (GetDescriptors) with this property.

This was what I've followed. Is this a correct procedure ?

There is a conflict in my mind with custom properties. For above explanation, What I am doing is to change property name for a field. I'm customizing only the apperance of the property name. This is not a custom field according to my opinion. This is a customized field. When I reference to your documentation and forum posts, I see the Custom fields are the new fields that does not exist in the object. So they are defined in the object.

In my case, My customized property  are generated by the tool (uses the changed property code) with new name.

Is it near to give a friendly name in Business Object Mapper and to follow our business ?

We have added a new feature to 1.6.5 that will allow you to rename the fields generated by the BOMapper... the underlying field in the database will remain the same, but the property that exists on the business object will be renamed.  We will be releasing it shortly.

Actually this won't be included in the 1.6.5 release.  It will, however, be in the maintenance release immediately after the 1.6.5 (i.e. 1.6.5.1 build).  There are several things that we wanted to get in the 1.6.5 build that are not going to make it due to time contraints and testing.  This one change will require a bit of testing and is something that we didn't want to change this close to the final release.  But it will be coming.