You’re offline. This is a read only version of the page.
288
The data is THERE, I've SEEN it. I just can't figure out why I can't SHOW it!
I have a Dataverse table InternalVBRF which has a default table view and Information form for data entry. Works well.
I created a Business Process Flow associated with this table called Budget Change Request
This automatically created a table called Budget Change Request Process.
And automatically created a Many/1 relationship between Budget Change Request Process and InternalVBRF
I edited the View of InternalVBRF
I go to the "Related" tab, choose Budget Change Request Process and choose to add the column Active Stage.
Once selected, it shows up in the view column, but does not display a value
If I go at it from the other direction (from a Budget Change Request Process view), Both sides are there -- the lnternalVBRF name (MLRTEST 12-5) and the current Active Stage (Initialization).
Why can't I get it to show from the InternalVBRF side -- is it because according to the relationship definitions, there are MANY related Budget Change Request Process records? (could you ever have more than one Active Stage?)
Is there any way to "get there from here"? Am I missing something?
It shouldn't be this difficult to pull in the current Active Stage for this record, esp when the relationships have already been defined!
@Fubar That's what I was afraid of. I was hoping there was some "trick" to configuring the data relationship that would allow it to return "first" (like in Oracle, you add Rownum = 1 to the WHERE clause) The "Active Step" value would be the same across all related records, so picking first would work in my situation.
Beyond frustrating that something so simple requires so much extra coding. Every time it enters a new stage, I would have to update the Request record's "Active Stage Text" value, which would in turn trigger On Modify triggers on the Request table... Was hoping to avoid that by leveraging the data relationship to get the value. I'll leave this open a few more days in case someone else has a different idea before marking this "can't be done" as the solution. Thanks so much for the response!
The relationship between the base Table and the BPF Table is 1:N (parent:child) - hence you cannot add something from the BPF instance into a view of the base Table (as per usual 1:N relationships in dataverse).
(you can add a field on to the base Table and populate it when the BPF stage changes, and then put that new field into your view)
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
17
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
