Get rid of condition if no property set is required
complete
A
Alexander Joslyn
When an information requirement is set without property set (e.g. LoadBearing instead of Pset_WallCommon::LoadBearing), Plannerly still exports the IDS with a condition expecting the property set to be named "NoPsetDefined". Instead, there should be no condition on the property set.
Clive Jordan
complete
New "Custom Settings" for IDS Exports now cover options that some IDS-receiving systems may not support.
Currently, this comprises:
- Export with Classifications
- Export with "NoPsetDefined" for missing Property Sets/Groups
Once Model/Task Rules are part of the IDS applicability criteria, this option will be accessible here too.
A
Alexander Joslyn
Clive Jordan would have been nice to clear this up before tomorrow's webinar ;)
Clive Jordan
Alexander Joslyn - Thanks for the reminder! Updated😊 - just a quick note on the reason behind this - some other systems faced issues in the past rejecting IDS files due to properties without Psets, so we included this feature. I completely agree that having it as an option is probably the best way to go. We've gone ahead and added it as an option for you. Now all you need to do is switch this option: