Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Custom Data deploy approach
Thiags
Environment : TS 6.5 Windows 2003 and OD 6.1.0
I have a Standalone data deploy scenario as follows :
We capture attribute values in the dcr as separate fields for building a plan.
for eg. to create a plan the user will enter values for attribute1, attibute2, attribute3, etc.. in the dct.
We will be inserting the values of the attribute as a separate record in attribute_values table like
attribute id, attribute name, attribute value.
Unlike the normal case wherein information catured in a dct will be deployed a table as a single record here each dcr field will be inserted as a new record in the table.
Information captured in the Plans dct need to be inserted in two different table.
Plan_header table will be updated with Plan id, name, etc.. while the attribute_values table will be updated as individual separate records for each attribute entered in the dct by the user
Is this acheivable using Data deploy. If you have worked on any such similar request can you throw some light on the approach.
Find more posts tagged with
Comments
Migrateduser
The dbschema is a bit restrictive but thanks to the fact that you can use raw SQL with DataDeploy (look up do-sql in the manual), pretty much anything is possible. I've just gotten over my dizziness from your explanation of what you need to do so my first thought would be to just do it that way... use transactional SQL in your DD conf instead of the dbschema method.
Migrateduser
You can also trick DataDeploy by creating a bogus root-group that doesn't contain any real data. Use path for the primary key in it, and don't put any other columns. Then your various attributes could go in a container that maps to a child group, and the pk on it could be something like path + isntance id.
I had to do that once to handle a situation where a customer wanted a single DCR that contained essentially a list of all the valid options for their products that could then be used to populate select boxes in other templates.