Monday, February 11, 2013

Model Version in Framework Manager





The way the versioning work is as follows - assuming you have versioning 
set to 3 

  • publish your package - version 1 
  • create reports - these reports will use package version 1 
  • publish the package - version 2 
  • create reports - these reports will use package version 2 
  • open reports which are using package version 1, these reports will validate with package version 2, and if saved will use package version 2 
  • publish your package - version 3 
  • create reports - these reports will use package version 3 
  • open reports which are using package version 1 or package version 2, these reports will validate using package version 3 and if saved will 
  • use package version 3 
  • publish your package - version 4 , this will overwrite version 1 of your package, so any reports using version 1 will now use package version 4 (the current package) 

I hope this helps. Most clients set version to 0 during development as 
this will only store 1 version of the package which will always be the 
current version!

1 comment:

  1. That's not true and you shouldn't copy someone else's work, especially when it's wrong. Setting to 0 means it will save unlimited versions. Saw this answer by someone else on a different site and it's sad you not only copy it, but you don't fix the error.

    ReplyDelete