Hi Max_V21, When you say "Dexterity based tables," I assume you mean SQL tables since this is what Dynamics uses now. Dexterity can write to other data storages, but I will assume the former. You can create tables in SQL, and use them in VST add-ins. The mechanism of how you access the data is up to you. The easiest solution is to write stored procedures, and use one of many ways to access the data in Visual Studio. This would require you to wrap your SQL objects around a "out of Dynamics" security layer though. If you wanted to create a fully integrated solution to Dynamics without using a database connection not provided by Dynamics, the option is still there, but it requires a lot more work. You would first create a table (with DEX_ROW_ID field) in SQL or in Dexterity first, and build your custom dictionary file. Then you would run it through the assembly generator to get the .dll for VST to interact with it. Once you reference the .dll, you would be able to use the Dynamics database connector to access the table without the need for something like SqlClient or other .Net ORM. I typically go for option 1 since it is easily the shortest route for building integrations.
↧