Open FilipSuster opened 1 year ago
@tedphillips could you perhaps have a look at it?
both com id's are still functionally valid for their appropriate use case.
pafe addin id is only in effect when co-running with cognos for microsoft office, otherwise if single-running - pafe should take the historical automation ID.
i'll double check the state of affairs, but i believe that's accurate.
will definitely take this as feedback of course, though unlikely to edit the historical samples to assume co-running - which is fairly rare today. rather than add a bunch of sophistication there, my strategy is that we should really be offering the vast majority our automation endpoints in global scope. ex: as macro-type udf's firstly.
apologies for the delay in response
which is to say, it should be operating as described in https://ibm.github.io/paxapi/#necessary-ibm-cognos-automation-api-references
Hello @tedphillips, thank you for your answer. I'm not that of an expert to know what you are talking about, but with my knowledge I have talked to people in our team and this is what we have figured out, so I just thought to let you know, because your sample macros simply didn't work for me and I made it working only by doing those changes described above. Thanks for considering it and you can close this ticket.
appreciated. I'm going to hold the item open for a while as I collect some information on any similar inquiries.
Bug Description Hello. In your docupedia https://ibm.github.io/paxapi/#macro-files there is a link to download two files which serve as an example to control IBM PA via macros in Excel. The file CognosOfficeAutomationExample.bas which contains the code has stopped working for me recently. My colleague has figure out that there is a bug in the "Public Property Get CognosOfficeAutomationObject" macro, where this line:
has an old name, which should rather be CognosOffice12.ConnectPAfEAddin, like this:
Would you please fix that in your example files?