@Anton_Loukine Fixed; thanks for bringing this to our attention. See: API Additions and Changes 2017-12-06.