4.0.0

Snowfakery 4.0.0

Drop support for Python versions 3.8, 3.9, and 3.10 (#1091)

Snowfakery v3.6.3

What's Changed

• Clean up warnings in tests and at runtime. by @prescod in #1027
• Clean up temporary directories after closing iterator by @prescod in #1029
• Make recent versions of pyright happy by @prescod in #1028
• Let mkdocs float by @prescod in #1031
• Let SQLAlchemy float by @prescod in #1032
• W17 Dependency updates by @jstvz in #1043

Full Changelog: v3.6.2...v3.6.3

Snowfakery 3.3.0

Snowfakery has a datetime_between function (#729)

Date-time values can now be coerced from strings and dates (#729)

Fixes to documentation (thank you @BrettMN) (#727)

find_record is now cached so that it only calls into Salesforce once. (#726)

Snowfakery 3.2

Snowfakery can now do random_reference to nicknames. (#639)

We removed some limitations on what Snowfakery can do with objects referenced through random_reference, especially using a.b.c.d syntax. (#681 and #639)

We added a unique option for random_reference to allow for 1-1 relationships across random references and no-duplicates many-to-many join relationships like Account->CampaignMember->Campaign (#684)

Snowfakery 3.1.0

When embedded in CumulusCI, Snowfakery can now do SObject Upserts. (#644)

Add a Decimal datatype (#631)

Output Boolean values using the JSON boolean type in JSON outputs. (#663)

Snowfakery 3.0.0

When embedded in CumulusCI, Snowfakery can now do SObject Updates. (#586)

Snowfakery can be used to do transformations of CSV files. (#586)

Snowfakery has a now function which returns a UTC datetime representing the present moment. (#485)

Snowfakery has a mode (snowfakery_version: 3) that lets formulas output types other than just strings. For example, they can generate date objects, which are amenable to date manipulations. This is an opt-in feature for the time being, but will become the default in June 2022. (#617)

Snowfakery has a debug function for inspecting expressions and values. (#613 and #615)

Snowfakery outputs "datetimes" in the UTC time zone, for better Salesforce compatibility. (#601, #694)

Snowfakery 2.5.0

Snowfakery now ensures that faked firstnames and lastnames are ASCII alphanumeric before attempting to incorporate them into a fake email (#597)

Snowfakery publishes a JSON Schema for IDE usage (#556)

Snowfakery gives a better error message if a CSV datasource has rows that have more columns than the header row. (#594)

Snowfakery 2.4.0

The Salesforce load order now follows the order of object template declarations in the recipe. The other considerations are described in the document (#563 and #566)

Improved syntax error messaging (#565)

Snowfakery 2.2

The unique_id and unique_alpha_code variables return a unique number that can be used to distinguish any record from others. For example, we can incorporate a unique ID into an email address or an employee ID. (#525)

Numeric and date counters are now available with the snowfakery.standard_plugins.Counters plugin. (#525)

Snowfakery will now accept UTF-8 CSV files generated from Excel with a Byte Order Mark (#516)

Snowfakery gives more detailed information in the snowfakery --version message (#469)

Booleans and dates can be the keys for random_choice lists. (#500)

Snowfakery 2.1

Fix an issue with datasets not being closed in an orderly fashion (PR #492)

Emails and usernames will now be generated to match firstnames and lastnames (PR #420)

Documented Salesforce.ProfileId function which looks up a Profile
in Salesforce by name and substitutes the ID automatically. (#438)