---
title: "DataSets and Projects not saving or visable"
canonical: "https://servicedesk.maxgeo.com/space/DS/1125712376/DataSets%20and%20Projects%20not%20saving%20or%20visable"
format: markdown
---
**Issue: **

DataSet or Project are not saving or visible in the admin portal.

![image](media://4e4daa32-896e-4794-9035-f882521f2a96)


**Cause:**

There are multiple causes that can cause the above issue:

- Missing Sort Orders or Duplicate sort orders
- Duplicate project ID
- Additional projects in the objects table
- Case sensitivity between DataSets and Projects tables

Run the below query(s) to identify the cause of the issue

```sql
SELECT * FROM tblSYSDataSet
SELECT * FROM tblSYSProject
SELECT * FROM tblSYSObject
WHERE TYPE = 'PROJECT'
```

**Resolution: **

**Missing Sort Orders or Duplicate sort orders**

Once the above script has been run check that the `tblSYSDataSets.SortOrder` and `tblSYSProject.SortOrder` are unique and NOT `NULL`

**Duplicate project ID**

Check that `tblSYSProject.ProjectID` are unique and NOT `NULL` and that `tblSYSObject.ParentID` for the projects match

**Additional projects in the objects table**

On rare occasions there can be Additional records in `tblSYSObject` where `TYPE = 'PROJECT'` These records should be removed from `tblSYSObject` 

NB: that the `tblSYSProject.Project_Name = tblSYSObject.Name` and `tblSYSProject.ProjectID = tblSYSObject.ParentID`

**Case sensitivity between DataSets and Projects tables**

In some cases the Project name against the Datasets has a miss match due to case sensitivity. This generally happens when Projects and/or datasets are either added or modified directly in the database.

The below script will update the Project in the DataSets table to match identically to the Project 

```sql
UPDATE D SET Project = P.Project
from tblSYSDataSet d
inner join tblSYSProject p
on d.Project = p.Project
WHERE D.Project <> P.Project COLLATE LATIN1_GENERAL_CS_AS
```


> ⚠️ DB Modification
> ⚠️ 
> ⚠️ Before any change is made to a user database (or system), maxgeo recommends competent staff should follow all standard database change management practices and never make untested changes to a production database.  
> ⚠️ Change, test and document all modifications on a test copy of your database to ensure results are as expected before implementing them on your live database. Always ensure a full backup is available in case rollback is required and follow all company change management procedures and practices.