Problem with version 5.0

If you are migrating from v4 to v5, I think they fixed this, but in the beta/Nightly I use this method:

But appear to be not related with this old issue.