Hi @tobias.koetter,
thanks for your quick reply. Unfortunately, I am not at all familiar with eclipse and I am still struggling. I set up the KNIME SDK as described in the [setup guide](GitHub - knime/knime-sdk-setup: KNIME Analytics Platform - SDK Setup and used the complete target. Then I included the source code in the target definition by ticking the “include source” check box as described.
Once I create a new node with the node wizard and inspect the code for the node model, there is the option to do right click on “Open Declaration” in order to see the function, as seen in the following screenshot:
However, when I try to import any classes from the Office 365 extension, the classes do not seem to be contained in the eclipse setup:
As a workaround I was able to add the file “org.knime.ext.microsoft.authentication_4.7.2.v202303211209.jar” from my usual KNIME installation to the build path setup in eclipse. This allows me to import the classes from the Office 365 extension:
Also I can add a Microsoft Credential port to the node model:
The problem with this workaround is that I get errors, once I want to add the created node in KNIME at runtime:
Is there any way to setup to adjust the target definition or to adjust the build path within Eclipse, such that I can import the Office 365 extension classes and inspect their source without my workaround?
P.S. I uploaded my existing workflow as Microsoft Dynamics 365 Business Central API Page Retriever on the community hub.
I discovered that there has been some discussion in the KNIME forum and if you reopen the topic, I will also post a link to my workflow there.