Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Packaging a custom inDB tool - Connectors remain green

FlorianTissen
6 - Meteoroid

Hi Community,

 

I created a macro that I now want to package with a custom UI etc. I read the articles about how to create the XML file but I keep failing getting things done.

My macro has an inDB input and inDB output. If I just add the macro to my workspace, it works fine and connectors are blue. In my packaged version, the connectors become green. The documentation does not give any hint what else could be the right attribute to change the connection type.

 

FlorianTissen_0-1574431550638.png

 

Another issue I have with this custom tool, is that it keeps telling me, that the macro wasn't found. I checked the name reference several time and even changed it, used copy/replace, but got no luck. The configuration XML file and the macro are in the same folder and I understand paths should be relative from there.

 

 

<EngineSettings EngineDllEntryPoint="inDB Dynamic Rename.yxmc" EngineDll="Macro" SDKVersion="10.1" />

 

 

FlorianTissen_0-1574432634323.png

 

Looking forward to read your thoughts and I hope for a solution. Thank you so far!

Florian

1 REPLY 1
DavidSta
Alteryx
Alteryx

Hi Florian,

 

within the configuration file you have the possibility to set a connection type. Within the docs is written to type "Connection", but this is not working for In-DB Tools.

If you set this connection type to "LockIn" the input is identified as In-DB (see this topic).

<InputConnections>
  <Connection Name="Data inDB Input" AllowMultiple="False" Optional="False" Type="LockIn" Label="I" />
</InputConnections>
<OutputConnections>
  <Connection Name="Output" AllowMultiple="False" Optional="False" Type="LockIn" Label="O" />
</OutputConnections>

 

The problem with not finding the Macro might be related to the engine settings part.

As described in the documentation you have to set the EngineDllEntryPoint. Within your configuration I can't see the "root"-directory of your tool.

Maybe you can modify it to something like this:

<EngineSettings EngineDllEntryPoint="MyToolDirectory\inDB_Dynamic_Rename.yxmc" EngineDll="Macro" SDKVersion="10.1" />

 

Labels