Question 52 — AB-620 Case Study Set
Review Paideffort's current Power Fx transformation.
ForAll(
Topic.RegResponse.results,
{
ContentText: regulationText,
ContentLocation: sourceUrl,
Title: regulationTitle
}
)
What must be changed before this result is supplied to Custom data? (Select one answer)
Rename
ContentTexttoContentwhile preserving the mappings forContentLocationandTitle.Rename
ContentLocationtoUrlwhile preservingContentTextandTitle.Rename
TitletoCitationNamewhile preservingContentTextandContentLocation.Replace the three named fields with one
Recordproperty containing the complete API object.
Correct answers
Rename
ContentTexttoContentwhile preserving the mappings forContentLocationandTitle.
Explanations
Correct Answer:
Rename ContentText to Content while preserving the mappings for ContentLocation and Title.
Explanation:
Paideffort's regulatory text must be supplied through the required Content column. The current transformation creates ContentText, which doesn't match the Custom data table contract. The source URL and regulation title are already mapped to the appropriate optional citation columns.
Wrong Answers:
Rename ContentLocation to Url while preserving ContentText and Title.
This would move the table further away from the required structure. Paideffort's citation URL belongs in ContentLocation.
Rename Title to CitationName while preserving ContentText and ContentLocation.
Title is already the correct optional citation-label column. The field that prevents the table from matching the required structure is ContentText.
Replace the three named fields with one Record property containing the complete API object.
Custom data expects specifically shaped table records rather than an arbitrary nested API record.