fix: stfc fap export access route fix#1530
Merged
Merged
Conversation
Bhaswati1148
approved these changes
May 22, 2026
ChongJiaChua
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes UserOfficeProject/issue-tracker#1598
Description
This PR addresses an issue with the STFC FAP export access route.
Motivation and Context
The change is required to correct the value retrieval for the 'Proposed_Route' and 'direct_access_route'. Previously, an incorrect property was being accessed which led to erroneous data being exported.
Changes
getStfcDataRowfunction.How Has This Been Tested
This change has been tested locally by running the FAP export function and verifying the exported data is correct.
How Has This Been Tested?
Fixes Jira Issue
https://jira.ess.eu//browse/
Depends On
Tests included/Docs Updated?