Details
-
Bug
-
Resolution: Fixed
-
Low
-
10.115.3
-
2
-
Severity 3 - Minor
-
No
Description
Issue Summary
On the [Feature] view, the below fields are from type NVARCHAR(350) and are named respectively:
- Custom Dropdown 1
- Custom Dropdown 2
- Custom Dropdown 3
As we can see on the schema:
| Table Name | Column Name | Primary Key | Null Text | Data Type |
|---|---|---|---|---|
| Feature | Custom Dropdown 1 | No | NULL | NVARCHAR(350) |
| Feature | Custom Dropdown 2 | No | NULL | NVARCHAR(350) |
| Feature | Custom Dropdown 3 | No | NULL | NVARCHAR(350) |
| Feature | FK Custom Dropdown List 4 | No | NOT NULL | INT |
| Feature | FK Custom Dropdown List 5 | No | NOT NULL | INT |
But on the [Feature History], the same fields are treated as FK, being of type INT:
- FK Custom Dropdown 1
- FK Custom Dropdown 2
- FK Custom Dropdown 3
As we can see on the schema:
| Table Name | Column Name | Primary Key | Null Text | Data Type |
|---|---|---|---|---|
| Feature History | FK Custom Dropdown 1 | No | NOT NULL | INT |
| Feature History | FK Custom Dropdown 2 | No | NOT NULL | INT |
| Feature History | FK Custom Dropdown 3 | No | NOT NULL | INT |
| Feature History | FK Custom Dropdown List 4 | No | NOT NULL | INT |
| Feature History | FK Custom Dropdown List 5 | No | NOT NULL | INT |
We can see the schema FK relationship, and we can see that they are not pointing/used on other tables:
| Table Name | Foreign Key Column Name | Referenced Table | Referenced Column |
|---|---|---|---|
| Feature History | FK Custom Dropdown 1 | Not Available | Not Available |
| Feature History | FK Custom Dropdown 2 | Not Available | Not Available |
| Feature History | FK Custom Dropdown 3 | Not Available | Not Available |
| Feature History | FK Custom Dropdown List 4 | Custom Field List | FK Custom Field List ID |
| Feature History | FK Custom Dropdown List 5 | Custom Field List | FK Custom Field List ID |
Steps to Reproduce
- Check the schema of the tables OR run a select on them
Expected Results
Columns would keep consistency between the tables.
Actual Results
Columns are of different types and names on the [Feature] and [Feature History].
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- resolves
-
ALIGNSP-17431 Loading...