March 21, 2016 at 12:48 pm #494836 BrianParticipant Thanks! Yes, upgrading the API resolved the issue for us. I really appreciate the quick turnaround with the fix.