How to migrate from GenAICommons.Connection to DeployedKnowledgeBase/DeployedModel in custom modules?
0
Hello, community! I’m facing a challenge while updating a Mendix app that uses the GenAICommons and snowflakeRESTSQL modules. Recently, GenAICommons was updated and the GenAICommons.Connection entity was removed, being replaced by DeployedModel and DeployedKnowledgeBase. In my case, the snowflakeRESTSQL module (specifically, the CortexAnalyst function) used the GenAICommons.Connection entity to manage connections. Now, I need to adapt the CortexConnection_Cast microflow (located in the CortexConnection folder of the snowflakeRESTSQL module), which used to cast to Connection, but this entity no longer exists. Some important points: According to the documentation, for knowledge base interactions I should use DeployedKnowledgeBase; for model invocation, DeployedModel. Both entities have similar associations to the old Connection, but DeployedKnowledgeBase is a concrete (blue) entity, while Connection was abstract (orange). When I try to replace Connection with DeployedKnowledgeBase in the microflow, I get the following error:The value is not of entity 'GenAICommons.DeployedKnowledgeBase' or a specialization. If I do the same with DeployedModel, the error does not occur. My questions: What is the correct way to migrate the use of Connection to the new entities, especially in microflows that used to cast to Connection? Is there a recommended approach for adapting custom modules (like snowflakeRESTSQL) to the new GenAICommons structure? Has anyone gone through this process and can share tips or examples on how to adapt microflows that depended on Connection? I appreciate any guidance or examples you can share!
asked
Nicolas Rossetto
1 answers
0
Hi Nicolas,
We're currently updating the SnowflakeRESTSQL module so it's compatible with the latest GenAICommons module.
Current version is only compatible with version 3.x of GenAICommons, see infobox after Prerequisites.
Best regards,
Emiel Paasschens on behalf of the Platform Integration Development team.