1 Reply Latest reply: May 15, 2014 10:14 AM by Grant Perkins RSS

    Question on correct procedure for adapting lookup calculated field

    MonUserCJ _



      I have a model that I'm using on a new report. The model contains calculated lookup fields. The input values for the lookup changed because the report I'm using the model is on is different.


      However, the mapping for the calculated field stays the same. This makes sense, but let's say I want to generate a mapping using the input values from the new report? Clicking "Get Input Values..." does not refresh the values.


      If I just delete and recreate the field it will mess up some other calculated fields. The best way I can think is make a second field, switch the names of the fields, and then delete the old field. Is there a better way? Thanks.

        • Question on correct procedure for adapting lookup calculated field
          Grant Perkins

          Is this V10?


          For background information, is this a duplicated copy of the original model or a re-use for the new report because the old report is not longer used?


          Do the lookup (I assume internal from reading the problem)  values conflict between the reports of could all values co-exist shoul dtha be desirable?


          Does "Get Input values" append the values found in the new report to the old values? Could you delete the existing entries and then update the values?


          In what way would deleting and recreating the field affect other calculated fields? In theory any calculated field relying on the lookup field should continue to work once the field exists again. However if the working of the calculation relies on the value returned in the field from the lookup you may have problems where lookup results are different - but of course you may have problems anyway if the values are different.


          If these lookups are consistent (but different) per report you could consider creating your own reference model of useful fields (and fuinctions and whatever else) and keeping each lookup set in there with unique identifying names.


          Your operational models (you would need 2 versions in this example) could then link the lookup field to the appropriate field from your User Defined source model. That way you have one main report model to maintain with a minor adjustment for one field between the 2 (or more) versions. However as described here I'm not sure you really need to go down that route. Separate models with their own internal lookup tables should work well enough.