unfortunately, there is not any available workaround for now and there is not any potential solution on going. For the typo on table 4 where it is mentioned that there is an existing workaround. It is just a typo on the errata sheet that I've escalated for correction on the coming release (under internal ticket number 196061).
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
