Overview

When you upload an image as a Static Resource in your development instance, even though the upload is successful, the image displayed in the UI is not the one that was uploaded.

This happens when the database refresh and the binstore refresh from the Production instance occur at different points in time, for example during the upgrade dry-runs. That causes a sync issue in the instance in which the binstore contains static files referencing static IDs that do not exist in the database.

Solution

If you have a Jive Hosted or Cloud instance, please contact us. For Jive on-premise instances, please follow the steps below:

1. Connect to your development instance's database.
2. Gather the maximum value of the staticID column from the jivestatics table through
   

   SELECT MAX(staticid) FROM jivestatics;

3. Confirm it has the same value as the id column in the following query's output. If the value is different then this solution will not apply.
   

   SELECT * FROM jiveid WHERE idtype=1140061448;

   Note: the value for idtype here refers to static resources in Jive. You do not need to change it in the query for static resources.
   <supportagent>
   Refer to the internal Enums and Such document for details on idtypes.
   </supportagent>
4. Gather the id value from the Production instance as well using the same query on the Production database. This provides a reference for the update that we will need to perform next.
   

   SELECT * FROM jiveid WHERE idtype=1140061448;

5. On the development instance's database run the following query.
   

   UPDATE jiveid SET id = <id value from production instance + 1> WHERE idtype=1140061448;

   Note: Incrementing 1 from the ID value from the Production database ensures that no references are being skipped or overwritten.

Testing

The uploaded static resource images should now be visible in the UI as well instead of the incorrect images.