@KWhelanNo it is not a mistake from your side. The solution @kaious suggested here is a good workaround for your use case.