Unfortunately, Freehand SQL views (like reports) are more immutable than their drag and drop counterparts. In order to add a field, the entire view will need to undergo validation a second time, which means that anything created on top of the original validation will be broken because the content it is getting replaced. Since Yellowfin does not delete records, opting instead to create new view and report entries within the database, the newly validated view will have a new ID and cannot be easily linked to everything that the old ID was.
The ticket you have referenced is slightly different but refers to the same concept. For now your best bet will be to export this content, change the view, then import the content back on top of the new view. As with my other suggestion, I would also look into creating this as a drag and drop view so that any future changes do not require this.
Please let me know your thoughts on this.
Regards,
Nathan
Hi Chad,
Unfortunately, Freehand SQL views (like reports) are more immutable than their drag and drop counterparts. In order to add a field, the entire view will need to undergo validation a second time, which means that anything created on top of the original validation will be broken because the content it is getting replaced. Since Yellowfin does not delete records, opting instead to create new view and report entries within the database, the newly validated view will have a new ID and cannot be easily linked to everything that the old ID was.
The ticket you have referenced is slightly different but refers to the same concept. For now your best bet will be to export this content, change the view, then import the content back on top of the new view. As with my other suggestion, I would also look into creating this as a drag and drop view so that any future changes do not require this.
I see there is already a ticket open for this problem under "Moving fields between categories errors".
I see there is already a ticket open for this problem under "Moving fields between categories errors".
Hi Chad,
Unfortunately, Freehand SQL views (like reports) are more immutable than their drag and drop counterparts. In order to add a field, the entire view will need to undergo validation a second time, which means that anything created on top of the original validation will be broken because the content it is getting replaced. Since Yellowfin does not delete records, opting instead to create new view and report entries within the database, the newly validated view will have a new ID and cannot be easily linked to everything that the old ID was.
The ticket you have referenced is slightly different but refers to the same concept. For now your best bet will be to export this content, change the view, then import the content back on top of the new view. As with my other suggestion, I would also look into creating this as a drag and drop view so that any future changes do not require this.
Please let me know your thoughts on this.
Regards,
Nathan
Hi Chad,
Unfortunately, Freehand SQL views (like reports) are more immutable than their drag and drop counterparts. In order to add a field, the entire view will need to undergo validation a second time, which means that anything created on top of the original validation will be broken because the content it is getting replaced. Since Yellowfin does not delete records, opting instead to create new view and report entries within the database, the newly validated view will have a new ID and cannot be easily linked to everything that the old ID was.
The ticket you have referenced is slightly different but refers to the same concept. For now your best bet will be to export this content, change the view, then import the content back on top of the new view. As with my other suggestion, I would also look into creating this as a drag and drop view so that any future changes do not require this.
Please let me know your thoughts on this.
Regards,
Nathan
Replies have been locked on this page!