﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>StrataFrame Forum » StrataFrame Database Deployment Toolkit » Enhancement Requests  » Default value for Deployment Data Wizard</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Mon, 18 May 2026 10:15:46 GMT</lastBuildDate><ttl>20</ttl><item><title>Default value for Deployment Data Wizard</title><link>http://forum.strataframe.net/FindPost24123.aspx</link><description>When using the Database Deployment Wizard, the "Deployment Data" step have all Data Packages selected by default.  In my daily work I have noticed that I always have to click the "Select None" in this step, since this is most needed when deploying data the first time, but when doing common data structure maintenance, in my case 99.9% these are not deployed.&lt;br&gt;
&lt;br&gt;
So the request is to have all Data Package not checked by default in the Database Deployment Wizard of the DDT.  See image attached.</description><pubDate>Thu, 06 Aug 2009 11:35:11 GMT</pubDate><dc:creator>Edhy Rijo</dc:creator></item><item><title>RE: Default value for Deployment Data Wizard</title><link>http://forum.strataframe.net/FindPost24138.aspx</link><description>[quote][b]Trent L. Taylor (08/06/2009)[/b][hr] So our future solution should meet both needs.[/quote]&lt;br&gt;
&lt;br&gt;
Sounds good to me, as generic as possible the better for everybody!</description><pubDate>Thu, 06 Aug 2009 11:35:11 GMT</pubDate><dc:creator>Edhy Rijo</dc:creator></item><item><title>RE: Default value for Deployment Data Wizard</title><link>http://forum.strataframe.net/FindPost24132.aspx</link><description>This entire dialog will be revisited in future releases.  Ultimately the selections (when running from within the designer) will retain the selections from the last time.  That should be a better solution that leaving them off or on as off may be better for you, but I know of other scenarios when on is better by default.  So our future solution should meet both needs.</description><pubDate>Thu, 06 Aug 2009 08:19:21 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item></channel></rss>