Are you just changing restriction attribute values? If so, are you changing them for all of your source features? What is the use-case scenario for why you are changing them daily?
If you wish to represent restriction attributes which are truly as dynamic as your scenario seems to suggest, without rebuilding the network dataset each time, then you can use a non-cached attribute evaluator to calculate the restriction attributes dynamically at solve time, as needed. This would not require a rebuild each time you update the values dynamically, as the rebuild process is only necessary for cached attribute values (such as those based on field evaluators). This is because attribute values for non-cached evaluators are not built into the network dataset. Rather, they are dynamically evaluated at solve time. Examples of non-cached attribute evaluators would be a VB-Script evaluator, a function evaluator, or a custom evaluator (created using custom programming).
VB-Script evaluators are simple to setup and use, but can be slow (and you are still somewhat limited in the data you can provide to them). Function evaluators for restriction attributes are limited to simple relational logic based on attribute parameters or constants. If you are trying to read custom data from some dynamic data source or you require advanced evaluation logic, and you wish to maintain relatively good performance, then I would suggest that you consider creating a custom-programmed evaluator for your purposes. I can provide you with some examples of custom evaluators, if necessary, once I know more about whether this is the best option for you, based on your responses to my earlier questions.
