This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
We did try to fix few cases in 8.5 where this used to happen
During the 8.5 development, we fixed 3 cases where we could easily get into this situation. Those were the ones we could reproduce and test. I guess this is another case that needs to be addressed. We will investigate the cause and will try to fix this soon.
The main reason this happens is because the view format has changed, but somehow the new view format is not retrieved when the view is opening (ends up using the cached version), and if the cached view format has fewer columns than what the view gets the data for (since the view index will be with the new view format which most often has additional columns for some new functionality added for that release). When this happens, we end up treating the row as a conflict row.
Feedback response number RPAL7NXDSP created by ~Denise Kiwesternivu on 02/04/2009