V1.5 SP 29.0

From FPDS-NG

Revision as of 15:42, 13 August 2025 by WikiSysop (talk | contribs) (Created page with "__NOEDITSECTION__ ==Schedule== <TABLE id="box-table-a" border=2> <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> <...")
(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)

Schedule

DescriptionStart Date End Date
Beta DeploymentSeptember 12, 2025September 12, 2025
Production Deployment September 20, 2025September 20, 2025

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryNo
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
ezSearchNo
Atom FeedsNo
Online HelpYes
User ManualNo

Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEMOD-48514 "isExistingOtherTransactionIDVComplete" returns wrong value when "Consortia" is blank The FPDS application shall be corrected so the isExistingOtherTransactionIDVComplete API returns ‘false’ and Validation Rule 9N01 (below), when the Other Transaction IDV provided has no value selected for "Consortia."
  • 9N01: "Consortia" is required for Other Transactions.

Currently, the isExistingOtherTransactionIDVComplete API returns ‘true’ and no error when the Other Transaction IDV provided has no value selected for “Consortia.”

Note: The isExistingOtherTransactionAwardComplete API returns ‘false’ and Validation Rule 9N01 when the Other Transaction Award provided has no value selected for “Consortia.”

Yes

Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEMOD-48670 “Unique Record Identifier” on FAADC Non-Aggregate records does not propagate to Amendments Currently, on Non-Aggregate and Non-Aggregate Individual FAADC awards, the “Unique Record Identifier” (URI) field is optional. When a value is entered in the “URI” field on the Base, the value does not propagate to new Amendments, and the field is open/editable while the Amendment is in 'New' status. This allows users to enter a different “URI” on the Amendment than on the Base, causing other propagation issues.

The FAADC application shall be corrected to propagate the value in the “URI” field on the Base of a Non-Aggregate or Non-Aggregate Individual FAADC award to each new Amendment and to lock the field while the Amendment is in ‘New’ status.

Yes
Retrieved from "https://beta.fpds.gov/wiki/index.php?title=V1.5_SP_29.0&oldid=5252"