Thread

What you’re seeing on staging v2 (planting summary still showing `N/A` even after you set `Selected location` and assign a bed) almost always comes down to one of these two things: the UI is still rendering an older / different “summary payload”, or the backend is persisting the bed/location change to a different object than the one the planting summary card is reading.

Based on the Tendgrow Planting Detail (v2) behavior around these steps, the most likely causes are:

1) The location/bed update saved successfully, but the planting summary UI didn’t refresh the dataset it uses
The “planting summary” card is populated from the planting detail data flow that’s tied to “planting growing location” (there are specific calls and data objects for this, e.g. `plantinggrowinglocation`, crop detail utilities, etc.). If the bed assignment happens through a different call/update path (or completes after the summary fetch), the card can stay `N/A` until the page re-fetches the correct summary payload.

How to verify quickly:
- Re-enter the planting detail page (leave + come back) and see if the summary then populates.
- If there’s any “refresh/recalculate” action after assigning bed, try that.

How to resolve:
- Ensure the bed assignment flow triggers a planting summary re-fetch/re-render (or updates the exact summary object the UI uses).
- If this is timing-related, enforce ordering in the frontend (wait for bed assignment completion before loading/refreshing the summary card).

2) Bed is assigned on one backend object, but the planting summary reads from `WSPlantingSummary` that didn’t get updated
There are explicit bed-assignment setters on other objects (e.g. `WSLocations.setAssignedBed`, `WSUnitConverter.setAssignedBed`), while the planting summary uses its own model (`WSPlantingSummary`). If staging v2 updates the bed on `WSLocations`/`WSUnitConverter` but `WSPlantingSummary` isn’t updated (or isn’t derived correctly from that bed assignment), the summary can remain blank/`N/A`.

How to verify quickly:
- Check whether any other part of the UI shows the bed/location correctly (location/bed section) while only the planting summary is `N/A`.
- Confirm whether `WSPlantingSummary` is missing/empty for that exact planting-growing-location context.

How to resolve:
- Update/derive `WSPlantingSummary` from the same bed/location source that the UI uses after selection.
- Or change the planting summary UI to render from the same object that’s being updated by bed assignment.

Notes on why this is plausible for your repro
The v2 planting detail code/data model includes distinct objects and calls for:
- selected location id (`WSListingResult.setSelectedlocationid`, `WSSoilTests.setSelectedlocationid`)
- bed assignment (`WSLocations.setAssignedBed`, `WSUnitConverter.setAssignedBed`)
- planting summary rendering (`WSPlantingSummary`)
And the “planting growing location” dataset is explicitly involved in the planting-detail lifecycle, so payload mismatch/refresh ordering issues are a common reason `N/A` persists.

If you want, tell me what exactly you see after bed assignment (does anything else on the page change besides the planting summary?), and whether the `Selected location` field is persisted before/after the bed assignment click. With that, I can narrow it to (1) refresh timing vs (2) backend object mismatch, and give you the precise fix direction.  

Sources (from Tendgrow Planting Detail v2): `ts:CropDataDetailComponent.api:1874`, `ts:CropDataDetailComponent.api:1792`, `ts:CropDetailUtil.api:301`, `java:com.tend.model.json.customResult.WSListingResult.setSelectedlocationid`, `java:com.tend.model.json.customResult.WSSoilTests.setSelectedlocationid`, `java:com.tend.model.json.customResult.WSLocations.setAssignedBed`, `java:com.tend.model.json.customResult.WSUnitConverter.setAssignedBed`, `java:com.tend.model.json.customResult.WSPlantingSummary`, plus prior related tickets `TEND-35987`, `TEND-33430`, `TEND-33328`, `TEND-32913`.