Thanks for your response! Based on your statement that "the order of the values in a Lookup dropdown column is determined by the ID field" from the source list, I first tried to sort the values in the source list based on the ID field, and that didn't work. The order of values in the Lookup column's dropdown remained the same.
It appears that the IDs in a Lookup Column are ALWAYS sorted in ascending order. In order to do a descending sort, one would have to reassociate those values with the IDs, so for example in my case, instead of value 1 relating to ID 1, it would need to relate to ID 8. Vice versa, value 8 would need to relate to ID 1.
I then resorted the values in Power BI, so that the last value would be related to ID 1, once it was drawn into the source list by a Power Automate Flow. That didn't work, because the flow contained an update step, which looked up on a key field that wasn't the ID.
To solve this issue, it appears I need to clear all values in the source list, and then run the power automate flow which will draw values from Power BI into the source SharePoint list. Instead of using update, a create step in the flow will be used, and then value 8 from Power BI will be drawn into the list as the first ID. Value 7 will be drawn into the list as the second ID and so forth.
The challenge with clearing out the values in the source list, is it will erase all the lookup values that were previously chosen by users. I tried it and had to go back and enter them again. I am reluctant to do it again.
Thus I am interested to see if there are any other thoughts on how to do this, or if the method I proposed above is the only way ...
Best,
Matren