0

Error with User Data

Colin Hynd

August 11, 2023 11:25

None

Follow

I have a report that is using 'user data' but some users occasionally receive the following error

 

------------------------------------------------------------------

'Error Loading user data for sheet 'Variations'

 

The user data cells $O$9 and $P$9 have been assigned duplicate keys. Each user data cell must contain a unique key. The offending key value is:

 

Key: VAR No., VALUECOST

Value: VAR 1, -2146826273

 

User data will not be saved for this sheet.

-----------------------------------------------------------------

The sheet is fairly complex (for me!) and does contain various keys/keynames, some of which are generated from data from Dynamics Nav. I cannot replicate on my machine so I don't think there are actually duplicated keys but I don't know how to resolve. The users having problems have viewer licences and I have a designer licence but I can't see how that would make a difference. I don't know where to start to resolve the problem.

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  CascadiaDataworks August 11, 2023 14:38

  -2146826273 is #VALUE so that is probably why it happens only some of the time.  Sometimes when the report runs, probably based on filters, there is a #VALUE returned, other times there are not.  In the case of the message, you have multiple #VALUES being returned which is why the key is breaking.

• 0
  
  Colin Hynd August 11, 2023 15:16

  Thanks for clarifying what -2146826273 means but I still can't understand why it is happening. When I run the report myself I don't get an error.

  In design mode those 2 cells are blank although columns are generated with corresponding unique keys when the report is run so I don't know if that could be connected. I've attached a screen shot with formulae which may help explain the setup. Their is no user data in cells O9 or P9 although there are numeric values in AE9 and AF9.

  

• 0
  
  CascadiaDataworks August 11, 2023 16:17

  I will freely admit that Stored User data, especially when using multiple columns is one of the most complex things to get right in Jet.  Usually the best method is to work with a consultant directly so they can see the report run, in the environment that it is running and causing issues.

  It's hard to really tell what is going wrong from screenshots, to be honest since we can't see the actual values generated.