It appears this was a bug with our REV 47. In 47 to fix the problem I had to select "APPLICABLE TO ALL INFORMATION MODELS".
↧
It appears this was a bug with our REV 47. In 47 to fix the problem I had to select "APPLICABLE TO ALL INFORMATION MODELS".