After far too long between, I’ve finally had a chance to release a new version of SchemaPuker

This release contains the following changes;

  • Objects are now shown with both their label and API name in the select list, entering objects in the text box is still done by API name only as before.
  • An issue with some custom object relationships not being drawn has now been resolved
  • Error handling has been further enhanced

It is live now at: https://schemapuker.herokuapp.com, so please give it a go!

As always, if you have any suggestions, comments, bugs or need help you can send me a tweet, leave a comment, or send me a message!


Also published on Medium.

3 thoughts on “SchemaPuker v0.3 Released!

  1. I’m trying SchemaPuker v0.3 for the first time but it does not recognize any custom object in my sandbox org. I’ve tried requesting several different custom objects and always get a similar error as this:

    [InvalidSObjectFault [ApiQueryFault [ApiFault exceptionCode=’INVALID_TYPE’
    exceptionMessage=’sObject type ‘Plan__c’ is not supported. If you are attempting to use a custom object, be sure to append the ‘__c’ after the entity name. Please reference your WSDL or the describe call for the appropriate names.’
    extendedErrorDetails='{[0]}’
    ]
    row=’-1′
    column=’-1′
    ]
    ]

  2. Hi Mick,

    Tried using the SchemaPuker Beta v.03 to generate a schema and for each generated line that ended in a number, an unneeded ” was added to the end of that line creating a parsing error

    Example:
    postgresql;ELSA;Salesforce;”Account (Account)”;”Shipping City (ShippingCity)”;20;”STRING”;40″

  3. Great talk at DF17 and very handy tool. Did a quick test and it works fine. Only problem I found was that it does not list the PricebookEntry object and if you enter it manually the relations from it does not seem to connect properly in the resulting ERD.

Leave a Reply

Your email address will not be published. Required fields are marked *