This is the fourth and final post in a series focused on Data Flow development.
Probably the most important tool used while developing software is the debugger. The debugger lets you step through your code and inspect the state of your program during runtime, so you can see what’s actually going on.
This post will focus on how to debug your custom class libraries while they are being executed by the Profitbase InVision Worker. For information on how to deploy your assembly (build and copy to target folders), you should read Part 1 of this series.
This is the third post in a series focused on Data Flow development.
In this post, we’ll continue using your Data Flow from Part 2, but instead of executing it from the designer and hard coding the message we’re writing to the database, we’ll create a Workbook with a text input field for entering the message.
This is the second post in a series focused on Data Flow development.
This post will show you how to create a parameterized Data Flow Item and execute it in a Data Flow. It’s a follow up to Creating and Deploying a custom Data Flow Item Class Library, so we’ll use the class library we created there. The way parameters are used, however, is exactly the same whether we use our own custom library or a built-in library.
This is the first post in a series focused on Data Flow development
Simply put, Class Libraries contains classes and methods that describe your business logic. Programs, such as Profitbase InVision, can execute class libraries after they have been compiled into assemblies (.dll) and linked to the program.