I am also having this issue. At the moment, I am re-importing the GIS polygon file and re-assigning n-values upon import. A bit cumbersome, but effective.
Hello.
This was a bug that I experienced as well. It appears to be corrected in version 5.0.4.