Rename Document file with a custom attribute

Ghazi, the filename is not an attribute (link data) property. It is a document property. You need to use ModifyDocument or ModifyDocument2 to change the filename. However, I do not know if this function also reaches out to the server and changes the actual filename. I hope it does, please test.

Dean, I know that. my question is i need to hook a costum attribute changes . and I sucess but the problem how to get document id.


if i get Doc ID then I will use ModifyDocument.

Regards
Ghazi

Wence,

I don't know what is "wrong" with your cast and I'm not in a position to troubleshoot it, but here's a cast that I've used before for something similar that works in C++:


 AADOCUMENTS_PARAM *paaParam = reinterpret_cast<AADOCUMENTS_PARAM *>(aParam1);

 TRACE( "ProjectNo: %ld\n", paaParam->lpDocuments->lProjectId);
 TRACE( "    DocNo: %ld\n", paaParam->lpDocuments->lDocumentId);

Hopefully, this will help you sort it out.

Hi Dan,

I just want to give GhaziKBR some ideas... aParam1 here is a pointer to AALINKDATA_HOOK_PARAM, not AADOCUMENTS_PARAM.

Can you please or let your Bentley colleagues help me out with my question "How to add Reference Info into Master File"? Thanks.

Sorry, I thought you were having a problem with your cast.  Yes, what you cast "to" is determined by which hook you are using.

As for help with references and MicroStation, I'll let someone else answer those questions as I haven't really done much with MicroStation for a while and someone else is likely to be able to answer your questions quicker and concisely.

Thanks for all of you , I resolved it and success getting Document ID, it was very simple

AALINKDATA_HOOK_PARAM const* pDocParam = reinterpret_cast<AALINKDATA_HOOK_PARAM const*> (aParam1);
lDocId = aaApi_GetDocumentId(0);
iProjId = aaApi_GetProjectId(0);


Regards
Ghazi

Ghazi,

I should warn you that the use of those two calls just happen to work and will probably work 99% of the time, but it is only because it is likely that ProjectWise has already put that information into the buffer that those calls are reading. (Check the documentation for the "proper" use of those calls).

You can get the document and project ids that you need directly from what is being pass to your hook function and you can be sure that it is correct.

In your hook, cast aParam1 something like this:

LPAALINKDATA_HOOK_PARAM pParam = (LPAALINKDATA_HOOK_PARAM)aParam1;

(You should also check what the value of aParam2 is for "defensive programming" so that you are only processing the operations that you know about. It is possible that additional processes could be added to a hook in the future. )

Then these values should be available to you:

pParam->lpLinkage->documentId.lProjectId

pParam->lpLinkage->documentId.lDocumentId

pParam->lAttributeRecordId

HTHs

Ghazi,

I should warn you that the use of those two calls just happen to work and will probably work 99% of the time, but it is only because it is likely that ProjectWise has already put that information into the buffer that those calls are reading. (Check the documentation for the "proper" use of those calls).

You can get the document and project ids that you need directly from what is being pass to your hook function and you can be sure that it is correct.

In your hook, cast aParam1 something like this:

LPAALINKDATA_HOOK_PARAM pParam = (LPAALINKDATA_HOOK_PARAM)aParam1;

(You should also check what the value of aParam2 is for "defensive programming" so that you are only processing the operations that you know about. It is possible that additional processes could be added to a hook in the future. )

Then these values should be available to you:

pParam->lpLinkage->documentId.lProjectId

pParam->lpLinkage->documentId.lDocumentId

pParam->lAttributeRecordId

HTHs

Hi Dan,

As I mentioned earlier, see above, when I tried:

LPAAEALINKAGE  lPLinkage = pDocParam->lpLinkage; //But can't get linkage. Don't know why?

So I can't get the likage, let alone documentId, why?

Thanks

Wence

Wence,

I would have to take a closer look at your code. Send me a private message and perhaps I can take a look.

I suspect that you are casting aParam1 to something that it isn't. What you should cast aParam1 to is dependent upon the hook type. In your posting, you said that you were setting a hook for AAHOOK_UPDATE_LINK_DATA. Looking at the documentation for that hook id you can see that aParam1 is defined as a pointer to a structure, and there is a difference (as you probably know) between LPAALINKDATA_HOOK_PARAM and AALINKDTA_HOOK_PARAM.

Also, if you are interested in the linkage, then you need to inspect the structure as it is defined as a union and its contents depend upon what type of linkage it is.

Hi Dan,

Please check your private message.

I think your casting way is the same as mine, we all got a pointer to AAHOOK_UPDATE_LINK_DATA. I tried to debug using your code. Still got the same error when tring to get the linkage. All other members are good, like ulMask, lTableId, lAttributeRecordId.

Yes, I get the same results. I'll try to find out an answer to the obvious question (is it a bug, or is the documentation wrong). I've used this hook before, but not for many years, so perhaps something has changed.

I believe the documentation for AAHOOK_UPDATE_LINK_DATA is incomplete. From notes I have in code that uses this hook, whenever the operation from aAparam2 is AAOPER_DOC_UPDATE_LINK_DATA, lpLinkage is not defined. This has also been my experience with it.

As you've already found, the only way to get the Doc Id in this scenario is to use aaApi_SelectLinksByAttr and then aaApi_GetLinkNumericProperty.