right now, if anything that goes into a pscustomobj for building the output is blank, it throws a console error, though the output still works. the console error is mitigated quite simply in particularly problematic outputs such as the email activity stuff, but UAL outputs are never 100% guaranteed to have all the data they are supposed to.
there MUST be a way to ensure that errors with ALL the PCO outputs do not throw console errors, and instead put some standardized information inside the output when it could not be found
right now, if anything that goes into a pscustomobj for building the output is blank, it throws a console error, though the output still works. the console error is mitigated quite simply in particularly problematic outputs such as the email activity stuff, but UAL outputs are never 100% guaranteed to have all the data they are supposed to.
there MUST be a way to ensure that errors with ALL the PCO outputs do not throw console errors, and instead put some standardized information inside the output when it could not be found