Okay, I'm managed to fix this by doing the following:

c:\www\cf-frameworks\modelglue_2.0.304\ModelGlue\unity\orm
\transfer>diff Transfe
rAdapter.cfc TransferAdapter-mine.cfc
288c288
<                       <cfset arguments.field.sourceKey = fields
[i].name />
---
>                       <cfset arguments.field.sourceKey = fields[i].alias />
296c296
<                       <cfset arguments.field.sourceColumn = fields
[i].name />
---
>                       <cfset arguments.field.sourceColumn = fields[i].alias />


But how do I know I haven't broken anything else by doing this? ;-)

On Mar 31, 4:36 pm, Andrew <[email protected]> wrote:
> Hi,
>
> I was hoping to take advantage of scaffolding to give me a head start
> in some functionality I'm currently adding to the user admin area of
> my site.  It uses Model Glue 2.0.304 and Transfer 1.1.
>
> However I've run into an issue as shown below:
>
> The relevant part of my Transfer.xml looks like this:
>
>                 <package name="admin">
>                         <object name="PermissionType" 
> table="ne_permission_type"
> sequence="NE_PERMISSION_TYPE_KEY_SEQ">
>                                 <id name="permissionTypeId" type="numeric"
> column="PERMISSION_TYPE_ID"/>
>                                 <property name="permissionName" type="string"
> column="PERMISSION_NAME"/>
>                         </object>
>
>                         <object name="EditorGroup" table="ne_editorgroup"
> sequence="NE_EDITORGROUP_KEY_SEQ">
>                                 <id name="editorgroupId" type="numeric" 
> column="EDITORGROUP_ID"/
>
>                                 <property name="groupName" type="string" 
> column="GROUP_NAME"/
>
>                         </object>
>
>                         <object name="Permission" table="NE_PERMISSION"
> sequence="NE_PERMISSION_SEQ">
>                                 <id name="permissionId" type="numeric" 
> column="PERMISSION_ID"/>
>                                 <property name="permissionName" type="string"
> column="PERMISSION_NAME"/>
>                                 <property name="int1" type="numeric"
> column="PERMISSION_KEY_VALUE_INT_1"/>
>                                 <property name="int2" type="numeric"
> column="PERMISSION_KEY_VALUE_INT_1"/>
>                                 <property name="string1" type="string"
> column="PERMISSION_KEY_VALUE_INT_1"/>
>                                 <property name="string2" type="string"
> column="PERMISSION_KEY_VALUE_INT_1"/>
>                                 <manytoone name="PermissionType">
>                                         <link to="admin.PermissionType" 
> column="permission_Type_Id"/>
>                                 </manytoone>
>                         </object>
>                 </package>
>
> When I accesshttp://localhost/admin/index.cfm?event=admin.Permission.edit,
> the scaffold fails with this error:
>
> Element PERMISSION_TYPE_ID is undefined in VALUEQUERY.
>
> When I turn on debugging I see that the query it has executed to
> populate the "PermissionType" dropdown is as follows:
>
> select PERMISSION_NAME as permissionName, PERMISSION_TYPE_ID as
> permissionTypeId from ne_permission_type
>
> However the generated scaffold code isn't using the aliased names:
>
>             <cfoutput query="valueQuery">
>               <option value="#valueQuery.PERMISSION_TYPE_ID#" <cfif
> sourceValue eq valueQuery.PERMISSION_TYPE_ID>selected</
> cfif>>#valueQuery.PERMISSION_NAME#</option>
>             </cfoutput>
>
> Does anyone want to know about this, or is it just scaffolding just a
> "proof of concept" that never went anywhere?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en

For more about Model-Glue, check http://www.model-glue.com .
-~----------~----~----~----~------~----~------~--~---

Reply via email to