Post

4 followers Follow
0
Avatar

Move data objects to another entity

Hi,

Is there any functionality available to move data objects attached to one entity to a different entity?

Thanks.

Fernando Borrego Polo Answered

Please sign in to leave a comment.

8 comments

0
Avatar

Hi Fernando,
Could you be more specific? Move which objects from what entity to what entity?
In general, if the data objects are attached to the original entity with a link, you could probably delete the link to the original entity and create a new link for the new one.
Hope this helps,
Ophir

Ophir Kenig 0 votes
0
Avatar

Hi Ophir,

I mean the entity called Data you added some months ago. It has a Source field where you specify the entity you want to attach the data object to on creation. However, this field is not editable and as far as I know there is no link involved that can be removed and replaced. Is there any way of performing this operation other than creating a new data object and copying all the values to it?

Thanks.

Fernando Borrego Polo 0 votes
0
Avatar

Hi Fernando,
You cannot change the SourceObject, but you can create other custom ref to object fields to link the data object and use them instead.
See http://usermanual.clarizen.com/data-object
Remember that permissions for the data object are based on the SourceObject
Hope this helps,
Ophir

Ophir Kenig 0 votes
0
Avatar

Hi Ophir,

That's exactly the problem we want to sort out. As the permissions derive from the Source Object, in some situations we need to change the attachments of the data objects to other tasks. Unfortunately I see there is no way of performing this operation.

Thanks for the information.

Antonio Moya 0 votes
0
Avatar

Hi Fernando,
Please submit a change request to make the SourceObject updatable. Apparently it is possible to change this field's behavior. A change request from a customer will help to promote it.
Thanks for pointing this out.
Ophir

Ophir Kenig 0 votes
0
Avatar

Thanks for the info Fernando.
Can you explain the use case? why is the DataObject first created on one object and then moved?
We usually don't allow moving "detail" object in a master-detail relationship because it usually doesn't make sense. For example, if you add a contact to a customer you can't move it to another customer. If you add a note to a work item, you can't move it to another case etc.
Data Objects are currently treated as a "detail" in that sense, so would love to hear your use case before we accept this CR

Eyal Post 0 votes
0
Avatar

Hi Eyal,

This is a bit complicated to explain but I'll try to summarize it. We have added a new task type that we call "recording session". This is used to track the work done by recording studios (localized voice over for our games). We used the data objects to track the lines to be recorded and they are always attached to the recording session task. The reason is related to permissions. The recording studios are our vendors (that is, external users) and they must only have access to their tasks, not the rest of the project. The structure of our projects is something like this (focusing only in the recording part):

  • Project -- Recording --- Recording Sessions ---- Session #1 ----- Session #1 - Spanish ----- Session #1 - French ----- Session #1 - German ---- Session #2 ----- Session #2 - Spanish ----- Session #2 - French ----- Session #2 - German ...

The vendors are assigned as managers to specific session tasks (i.e. Session #1 - Spanish) so they can edit certain columns in the data objects (we would prefer if they could do so as resources but it seems currently it's not possible https://success.clarizen.com/hc/communities/public/questions/206743807-Who-can-edit-data-objects-). The data objects are then attached to these tasks too (so the Spanish vendor only has access to its lines). What's the problem with this setup? We have a couple of them actually:

  • First of all, from our internal tools we generate recording scripts that are then transformed and imported into these data objects. When the scripts are generated, we still don't know when they will be recorded, so we don't know in which session they will end up. In this case we would like to be able to attach the lines to any other task (i.e. the parent "Recording Sessions") and allow the users to move them to the corresponding task once they know the dates.
  • Secondly, some lines can be moved to other sessions. For instance, a voice over actor gets sick during the first session so the recording managers in our side decide to move the lines to the second one. There are several reasons for this move to be necessary and right now our only option is to clone the lines.

Does this clarify our process? Would you need any more details?

Thanks.

Fernando Borrego Polo 0 votes
0
Avatar

Thanks for the explanation Fernando. As suggested, please open a CR and we'll try to promote internally.

Eyal Post 0 votes