As of April 17, 2018, this site is now in read-only mode. To start new Blackbaud Developer’s discussions, you will find Developer Discussions in the Blackbaud CRM Community.

To post or respond to Blackbaud Community discussions, you will have to login using a login. Learn how to login here. If you have questions or need assistance, please email

1.7k questions

3.2k answers

401 users


1.7k questions

3.2k answers

401 users

I was just wondering if the answer from this 2012 question is still the best way to go for pre-populating a table during catalog load.

if you're using a build/deploy process you could also roll the SQL
statement execution in with the customization load. MSBuild is a
particularly attractive option since there are MSBuild tasks included
with the BB CRM that can make config load, customization load, and SQL
execution easier.

If you went this route, the MSBuild tasks are located in the
assembly. A few we've found useful are "ExecuteSQL",
"ImportConfigurationData", and "LoadCatalogItem".

asked by mitchgibbs (153 points)

1 Answer

Best answer

Yes, although that's the best option during a build. I usually just create record operations and run those if I don't have direct access to the database.

answered by chriswhisenhunt (3.9k points)
selected by mitchgibbs

Makes sense. Thanks, Chris.