Problem is solved after updating D365 into 10.0.2
↧
Problem is solved after updating D365 into 10.0.2