Datafile enhancement allowing default setting for field not in datafile.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Datafile enhancement allowing default setting for field not in datafile.

BJ Freeman
I have a suggestion:
1) lot of the datafiles should have the ability to have set value fields
that need to be filled in as they are converted to entities.

and example is Product
the Datafile may not have the field chargeShipping which is default N
so to put in a Field with and attribute value which tells the datafile
import to just pass this thru but not read the datafile for this.
this way the xml output will have the field chargeShipping="N"
or
 productTypeId="FINISHED_GOOD" which really is not a default but should
be filled in during the import of the xml. The datafile usually does not
have such information in it.

Or did I miss something?
any suggestions before I make a patch?

I thought about putting in defaults in to the minilang new entity or and
EECAS but that takes a lot more than just working on the datafile
component.  I am not ready to take on such a task.
:D

--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

Reply | Threaded
Open this post in threaded view
|

Re: Datafile enhancement allowing default setting for field not in datafile.

BJ Freeman
Ok really trying to use the datafile.
so far is seems ignore, default-value, do not work.
so will see what I can do to make this viable.
here is the senario.
I have a supplier file that has information that goes in many different
entities. the Files are usually tab delimited.
So I created a record for each.
the problems is ignoring all the columns thru pass. that is what ignore
is suppose to do. would be easier if you can specify a column to use for
the output.
any way if somone wants to chime other wise will make a jira with my
contribution

BTW Happy Memorial day for those in the US.


BJ Freeman sent the following on 5/24/2009 1:19 PM:

> I have a suggestion:
> 1) lot of the datafiles should have the ability to have set value fields
> that need to be filled in as they are converted to entities.
>
> and example is Product
> the Datafile may not have the field chargeShipping which is default N
> so to put in a Field with and attribute value which tells the datafile
> import to just pass this thru but not read the datafile for this.
> this way the xml output will have the field chargeShipping="N"
> or
>  productTypeId="FINISHED_GOOD" which really is not a default but should
> be filled in during the import of the xml. The datafile usually does not
> have such information in it.
>
> Or did I miss something?
> any suggestions before I make a patch?
>
> I thought about putting in defaults in to the minilang new entity or and
> EECAS but that takes a lot more than just working on the datafile
> component.  I am not ready to take on such a task.
> :D
>

--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

Reply | Threaded
Open this post in threaded view
|

Re: Datafile enhancement allowing default setting for field not in datafile.

BJ Freeman
In reply to this post by BJ Freeman
https://issues.apache.org/jira/browse/OFBIZ-2518
I have added documentation to the datafile.xsd
Plus added .a patch so you can see what I added easier
if someone can flll in what I could not from the code I would appreciate it.
I will then start on the code changes.
thanks

BJ Freeman sent the following on 5/25/2009 10:02 AM:

> Ok really trying to use the datafile.
> so far is seems ignore, default-value, do not work.
> so will see what I can do to make this viable.
> here is the senario.
> I have a supplier file that has information that goes in many different
> entities. the Files are usually tab delimited.
> So I created a record for each.
> the problems is ignoring all the columns thru pass. that is what ignore
> is suppose to do. would be easier if you can specify a column to use for
> the output.
> any way if somone wants to chime other wise will make a jira with my
> contribution
>
> BTW Happy Memorial day for those in the US.
>
>
> BJ Freeman sent the following on 5/24/2009 1:19 PM:
>> I have a suggestion:
>> 1) lot of the datafiles should have the ability to have set value fields
>> that need to be filled in as they are converted to entities.
>>
>> and example is Product
>> the Datafile may not have the field chargeShipping which is default N
>> so to put in a Field with and attribute value which tells the datafile
>> import to just pass this thru but not read the datafile for this.
>> this way the xml output will have the field chargeShipping="N"
>> or
>>  productTypeId="FINISHED_GOOD" which really is not a default but should
>> be filled in during the import of the xml. The datafile usually does not
>> have such information in it.
>>
>> Or did I miss something?
>> any suggestions before I make a patch?
>>
>> I thought about putting in defaults in to the minilang new entity or and
>> EECAS but that takes a lot more than just working on the datafile
>> component.  I am not ready to take on such a task.
>> :D
>>
>

--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.