SourceColumnName does not exist in Adapter model

private EntityBase2 _EnterpriseEntity = null;

for ( int i=0; i<_EnterpriseEntity.Fields.Count; i++ ) { if ( ( _EnterpriseEntity.Fields[i].SourceColumnName != "PERSON_ID" ) && (
_EnterpriseEntity.Fields[i].SourceColumnName != "WEB_APPLICATION_ID" ) ) { _EnterpriseEntity.Fields[i].CurrentValue = _EnterprisePrefs [_EnterpriseEntity.Fields[i].SourceColumnName]; } }

hommels wrote:

SourceColumnName does not exist in Adapter model

private EntityBase2 _EnterpriseEntity = null;

for ( int i=0; i<_EnterpriseEntity.Fields.Count; i++ ) 
{
           if ( ( _EnterpriseEntity.Fields[i].SourceColumnName != "PERSON_ID" ) && (  
                 _EnterpriseEntity.Fields[i].SourceColumnName != "WEB_APPLICATION_ID" ) )
           {
    _EnterpriseEntity.Fields[i].CurrentValue = _EnterprisePrefs 
                         [_EnterpriseEntity.Fields[i].SourceColumnName];
           }
}

I could be wrong on this one, but I believe that that information is not accessible from within the entity itself. The reason is that the persistence information (source table, column, etc) is abstracted from the entity itself. You'll find methods of accessing that information within the DataAccessAdapter in the DatabaseSpecific project of the generated code. Check the PersistenceInfoFactory class.

I am curious, however, why access to the column name is required instead of using the entity's property name? You can use _EnterpriseEntity.Fields["PERSON_ID"] instead of attempting to reference the column name, or better, _EnterpriseEntity.Person_ID.

Jeff...

i need to get at a specific (i from the index)sourcename property from the collection

hommels wrote:

i need to get at a specific (i from the index)sourcename property from the collection

Well, assuming the generated property name wasn't changed from the original column name in the Designer, you can use

_EnterpriseEntity.Fields[i].Name

Jeff...

Hommels, you're trying to use adapter with selfservicing code. That won't work. Either use Selfservicing code or use adapter. Adapter has a different design pattern, that's why there are two different paradigms provided.