CBCopyPost

yaronlu · 2022-07-26T06:58:22+00:00

There was an error rendering this rich post.

Hi,

We are using oscript to try and get category info of the target folder inside CBCopyPost event.

It seem like the object holding this information is not located in the regular local variables list.

It is important to mention that we dont want to be dependent on the option of the category metadata that is manually chosen when you copy file on the cs web IDE.

When I try to use copyInfo to get the target node metadata, it returns null:

Psaudo code:

                                               DAPINODE    ndCurrNode = DAPI.GetNodeByID( prgCtx.DSession().fSession, DAPI.BY_DATAID, CopyInfo.NewNode.pID )
                                               if isDefined (ndCurrNode ) && isNotError ( ndCurrNode )
                                                           Object llNode = $LLIAPI.LLNodeSubsystem.GetItem(ndCurrNode.pSubtype )
                                                           result =           llNode.NodeCategoriesGet( ndCurrNode )

Can you please post some example of how to get target category metadata on a copy event?

Thanks ,

Yaron

Find more posts tagged with

Comments

Dave Carpeneto

Assuming what you're looking to do is override a function with the following signature:

      	override function Assoc CBCopyPost( \
		Object		dapiCtx, \
		DAPINODE	node, \
		Assoc		copyInfo, \
		Dynamic		context )

... the first step to figure out what is happening is to set a breakpoint in CSIDE in the first few lines of your function so that you can inspect copyInfo to see what you got passed in 🙂

yaronlu

Thanks for your fast reply Dave!

I already inspected the copyInfo object, but could not figure out where is the metadata of the target container, so I can copy the target category to the empty category of the file I am copying.

I will try to clear things a bit..

My problem is that when I copy a file from a folder without category, to a folder that has a category,

I end up with a copied item that has no category.

I would like to be able, in oscript, to get a hold of the populated target folder, so I can copy manually its Metadata to the copied item.

Maybe there is a temporary object created only for the transfer, and therefore I am not looking at the right object?

I will appriciate if you can suggest some way I can follow so I will be able to identify in oscript the final target container object.

Thanks,

Yaron

Hans Stoop

Hi Yaron,

When the user copies an document they can specify how the categories are handled. You can debug the standard code to see what is specified to make that happen.

You should be able to just specify it in the copyinfo when calling the NodeCopy function. I expect it is

copyInfo.AttrSourceType = $LLIAPI.AttrSourceDestination

Hans

yaronlu

Thanks Hans, I tried to follow your advice by adding AttrSourceDestination as my source type.

But unfotunately, I get the hook function too late in the process.

Meaning if the user left the default "AttrSourceDestination=original" option and continue the copy process, I cant make the proprty screen pop out as if he selected the other target destination options.

So for now we guided the customer to make sure he choose the "AttrSourceDestination=taget" manually before copying.

Now the copy is handled fine by using the CopyInfo.NewNode instead of node.

But when I try to apply this logic also on the Move process, It seem to be an entire different issue.

First of all, it has nothing like"MovedNode" object, that I can replace with node in case of "Move".

Can you please help me get the right object to use on "Move" command, so I can handle its attributes like in the copy command?

Thanks

Hans Stoop

I would expect that you can implement it in the CBCopyPre callback.

For move you only have the original object, which is the node parameter.

Hans