Nondeterministic functions such as RANDOM(), CURRENT_TIMESTAMP(), and NOW() can cause TabCompare to identify differences that are not indicative of a defect or unexpected results. A nice-to-have feature would be a call to the Metadata API that identifies if there are any such functions upstream of the viz in question. Simply identifying that there are such functions involved in the output report would be sufficient to handle them appropriately in the analysis workbook--we'd still compare the differences, but we could decrease the value indicating the likelihood of a true issue so that the admin can choose to skip investigating them.
Nondeterministic functions such as RANDOM(), CURRENT_TIMESTAMP(), and NOW() can cause TabCompare to identify differences that are not indicative of a defect or unexpected results. A nice-to-have feature would be a call to the Metadata API that identifies if there are any such functions upstream of the viz in question. Simply identifying that there are such functions involved in the output report would be sufficient to handle them appropriately in the analysis workbook--we'd still compare the differences, but we could decrease the value indicating the likelihood of a true issue so that the admin can choose to skip investigating them.