Answer
Yes — this specific error has been traced to a genuine case-sensitivity inconsistency on some screens, where the Logical Unit's own base view name is registered internally in ALL CAPS, while that same screen's Data Source view-name property is instead stored with Initial Capital Letters — a mismatch that trips this exact error even though the two names refer to the same underlying view. This has been corrected for specific windows in later updates (standardizing both to ALL CAPS), but if you hit this exact error on a screen that hasn't been patched yet, it's worth reporting to IFS as this known class of case-mismatch issue rather than assuming it's a configuration mistake on your end.