In addition to a great post by Eddie at http://tdiingoutloud.blogspot.com/2011/02/portable-solutions.html
Here's an additional option of making a solution easily portable/testable between QA, Dev, and Production environments.
When developing within the TDI Config Editor we want to make the most of the flexibility provided in Eclipse. In this example we want to create a Property store for each environment which you'll be testing your Assemblyline against.
Here's an example of my Property Stores:
-- Script References:
When referencing an property from a Property Store...reference the Property Name only.
Not the Property Store Name. With out declaring the Property Store Name, the TDI Server will pull the value from the Default Property Store. Use setParam(string), not setParam(String,String) when referencing the property.
Not the Property Store Name. With out declaring the Property Store Name, the TDI Server will pull the value from the Default Property Store. Use setParam(string), not setParam(String,String) when referencing the property.
-- 'Use Property' Reference:
When setting the value of a Connector's Field, there's many different ways to do this.
I believe the easiest approach is the 'Use Property' option.
When using the 'Use Property' option of a Field definition you'll see it automatically adds the Property Store Name to the Property Name. This occurs when you select the property from your available properties.
By removing the Property Store Name (in the above example it would be 'Customer_Test:') the server will pull the Property Name from the Default Property Store.
-- Setting the Default Property Store
Now that we've set the solution to read the values from the Default Property Store, and not a particular Property Store we can easily and quickly redirect the direction of an AL just by selecting which Property Store we indicate as the Default Property Store.
To set the Default Property Store, just right click any of your Property Stores and select 'Default Property Store'.
On your next AL execution, the AL will read all it's property values from this particular Property Store.
-- Required Environment:
I believe the easiest approach is the 'Use Property' option.
When using the 'Use Property' option of a Field definition you'll see it automatically adds the Property Store Name to the Property Name. This occurs when you select the property from your available properties.
By removing the Property Store Name (in the above example it would be 'Customer_Test:') the server will pull the Property Name from the Default Property Store.
-- Setting the Default Property Store
Now that we've set the solution to read the values from the Default Property Store, and not a particular Property Store we can easily and quickly redirect the direction of an AL just by selecting which Property Store we indicate as the Default Property Store.
To set the Default Property Store, just right click any of your Property Stores and select 'Default Property Store'.
-- Required Environment:
