Warning

JUser: :_load: Unable to load user with ID: 1005

0
I would like to change a Single Selection field to a Single Relational field in a deployed Mashup.

Has anyone ever updated the ts_fields table (and dependencies) to make this type of change? Is there a supported method for doing this?
Responses (6)
  • Accepted Answer

    Tuesday, October 09 2012, 08:20 AM - #Permalink
    0
    I have changed a field type before and had a few things I had to do to insure proper operation.I think I changed a meo to a fixed text or vise versa, not only did I have to update the field type value I had to change the table structure as well. Obviously Serena won't support this. Also I made my changes with an empty field it was a mistake made back in TT days and there was never any data loaded. I would think changing a single selection to single relational would be much more difficult. What version of SBM are you running? Couldn't you just delete the field, create a new field as needed. You could also then take the data loaded for the single selection and migrate it to the single relational but you'd have to know what you are doing.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 09 2012, 08:58 AM - #Permalink
    0
    Thanks Mike,

    We're running Serena Business Mashups 2009 R1.03.

    I agree that deleting and creating a new field would be a better solution, but the customer relies on reports against the database and hoped the values stored would be similar/identical.

    It sounds like it would be more work than it's worth.

    Here's Serena's response: It is not currently possible to change a field type after deployment.

    There is an enhancement in [ENH148745], requesting that this functionality be added, and it is linked to this case so that you can be notified as the feature is added in a future release.

    You can currently delete the field you have added, and add the one you intended.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 09 2012, 09:27 AM - #Permalink
    0
    Yeah Serena has to say that. What they mean is it's not a supported thing to do. It certainly is possible as I have done it. You have to really understand the data though and the table structure. I don't think I would attempt changing from single selection to single relational but as I said it wouldn't be that difficult to add the new field copy the data over only now it's link data instead of selection data it also matters what table you are pulling the single relational from, like single relational to an aux table or to a primary table. There's not a lot to go on. Regardless of the approach you'll need to update all reports to reflect the new field and remove the old hopefully there wouldn't be many of these.
    The reply is currently minimized Show
  • Accepted Answer

    Jeff Malin
    Jeff Malin
    Offline
    Wednesday, October 10 2012, 07:32 AM - #Permalink
    0
    RE: "the customer relies on reports against the database"... it might be helpful to explain to the customer that the effort involved in modifying their database queries will almost certainly be less than the effort to alter the database columns, adjust the back-end configuration, figure out what to do with change history, and deal with any problems that arise.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, April 09 2013, 05:53 AM - #Permalink
    0
    I was able to via access find and replace the column in the users reports from the deleted field to the new field. and then re-start IIS. then the users didn't notice any change.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, April 09 2013, 05:55 AM - #Permalink
    0
    It's teh TS_columns in teh TS reprots table. you'd have to get the ts_id from the ts_fields table to know what number you are changing from / to.
    The reply is currently minimized Show
Your Reply

Recent Tweets