---
title: "Contract Project Area entries not displaying after Save"
canonical: "https://servicedesk.maxgeo.com/space/DS/2010677250/Contract%20Project%20Area%20entries%20not%20displaying%20after%20Save"
format: markdown
---
#### Here’s the revised **Knowledge Base article** incorporating details from the image:

---

### **Issue: Data Not Displayed in Front-End After Import**

#### **Summary**

When data is imported into the `dbo.tblContractProjectArea` table without a `DataSet` value, the records do not appear in DataShed5. This occurs because the `DataSet` column in the table is **nullable**, allowing records to exist without an associated `DataSet`.

#### **Table Structure**

The issue relates to the following table and columns:

**Table:** `dbo.tblContractProjectArea`  
**Key Columns:**

- `ContractID` (PK, FK, nvarchar(20), **not null**)
- `Project_Area` (PK, nvarchar(25), **not null**)
- `Site` (PK, nvarchar(25), **not null**)
- `DataSet` (FK, nvarchar(30), **nullable**)

**Other Columns:**

- `Description` (nvarchar(1000), not null)
- `Is_Active` (bit, not null)
- `Sort_Order` (int, nullable)
- `Data_Source` (nvarchar(255), not null)
- `Load_Date` (datetimeoffset(0), not null)
- `Loaded_By` (nvarchar(50), not null)
- `Modified_Date` (datetimeoffset(0), nullable)
- `Modified_By` (nvarchar(50), nullable)

#### **Root Cause**

DataShed5 automatically filters records based on the **active **`DataSet`** selection**. If a record does not have a `DataSet` value, it will not match the filter criteria and therefore will not be displayed.

#### **Impact**

- Records imported without a `DataSet` are present in the database but remain invisible in DataShed5.
- This is a **data integrity issue**, not an application defect.

#### **Resolution**

There is no change required on the application side. To ensure visibility in DataShed5:

- Include a valid `DataSet` value during data import.
- Alternatively, update existing records to assign the appropriate `DataSet`.

#### **Best Practices**

- Validate input files before import to ensure `DataSet` is populated.
- Use scripts or ETL processes to assign default `DataSet` values where applicable.
- Communicate to data providers that `DataSet` is critical for DataShed5 visibility.