I noticed that when declaring feature-wise property values for validStartDate and validEndDate import/update requests get rejected when validEndDate property value is null for one or more feature.
Actually the KomMonitor Data Management API allows validEndDate to be null on both, the global validEndDate as well as the feature-wise property.
I made a quick fix using a try catch block in commit 6b4984982c73d66b7d01d9e97ec3b36772449b3b
You may revise it and suggest/implement a better solution.
I noticed that when declaring feature-wise property values for validStartDate and validEndDate import/update requests get rejected when validEndDate property value is
null
for one or more feature.Actually the KomMonitor Data Management API allows validEndDate to be
null
on both, the global validEndDate as well as the feature-wise property.I made a quick fix using a try catch block in commit 6b4984982c73d66b7d01d9e97ec3b36772449b3b
You may revise it and suggest/implement a better solution.
Regards, Christian