This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Has anyone ran into this before? In a try catch using JSON.stringify to log the error details is logging an empty JSON object. In this example I force an error and log to error messages. The first one uses the object to log the properties, the second one tries to use stringify.

(If it matters this is a map/reduce 2.1 script.)
```try {
    // force an error
    blah.breakme();
} catch (e) {
    log.error({
        title: `This works as expected`,
        details: {
            message: e.message,
            name: e.name,
            stack: e.stack,
        }
    });
    log.error({
        title: 'This logs an empty JSON object {}',
        details: JSON.stringify(e)
    });
}```

<https://system.na0.netsuite.com/app/help/helpcenter.nl?fid=section_158755248128.html#subsect_158755291553|Error Object Properties>

Well that's disappointing but that's exactly it. Thanks!

For others that find this post. If you're looking for functionality similar to 2.0, stringify has a 2nd parameter, replacer, that helps us out.
```log.error({
    title: 'This logs an empty JSON object {}',
    details: JSON.stringify(ex, Object.getOwnPropertyNames(ex))
});```


that only captures _owned_ properties. If you have lodash handy (we always do) we use `_.toPlainObject()`