With Price From Attribute you do not type an amount: you pick a number field and the value the applicant enters (or the form calculates) is charged. Typical SRDs: customs duty equal to the declared value, a donation of any amount, a fee equal to an assessed total.
▶ Video walkthrough in the Rise course.
The form asks Donation Type (General Donation, Program Sponsorship, Event Participation). For a general donation it shows General Donation Amount (number, minimum 1,000); for an event it shows Event Fee (number, 5,000 to 500,000).

The donation form: one number field per donation type

Scenario 1: price from the General Donation Amount field, when Donation Type is General
Mixing attribute and value scenarios in one service
| Scenario | Set Price To | Source / amount | When |
|---|---|---|---|
| 1 | Price From Attribute | General Donation Amount | Donation Type = General Donation |
| 2 | Price From Attribute | Event Fee | Donation Type = Event Participation |
| 3–5 | Price Value | 50,000 / 75,000 / 100,000 | Donation Type = Program Sponsorship AND Program = each program |
Gotcha · only number fields, and never empty
The source must be a number field. Give it a minimum and maximum in the form so nobody pays 0 or 1012. The scenario that uses a field must only match when that field is shown: if the field is hidden, its value is missing and the price cannot be read.
Artisans set their own item price in the field itemPrice, and the buyer pays exactly that. How do you configure the price?
D. When the applicant supplies the amount, the field is the price: one scenario handles every possible amount.