Looking at your code, I'm assuming that the dual list box shows up as shown in screenshot below. Note the empty highlighted option under the Available section.
The dual list box sees the entries to be used, but can't parse it into a label & value. Refer here,
Description: A list of options that are
available for selection. ...
As mentioned here, you cannot set aura:id value dynamically.
aura:id doesn't support expressions. You can only assign literal
string values to aura:id.
But you could manage to implement the following approach:
Set same aura:id for all the lightning:input elements; so when you query by this ID, you will get an array of these elements [in the same order ...
I initially assumed, given that you're sending back a Map<String, Object>, the parser is not intelligent enough to try to map an Object to the appropriate type. Couple that with not all Apex primitives being given a representation in JSON (Dates and DateTimes for example are ISO timestamps as strings) and you're going to run into some limitations ...
A modal would be very easy in this case.
Create a new component named as LightningFlow
<aura:component description="LightningFlow" implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction"
.js controller or helper
const map1 = new Map();
lightning:isUrlAddressable is an Aura interface and this link states the following:
The lightning:isUrlAddressable interface extends the
lightning:hasPageReference interface. A component that implements
lightning:isUrlAddressable then gets access to the page state through
the pageReference attribute. The page state is a representation of the
current URL ...
You can use window.open method once the URL is generated and the promise is resolved, to navigate using the NavigationMixin.
Try the below code
//Navigate to pdf page
this.PageUrl = '/apex/AVFpage_HTML';
this.PageUrl += "&accountId="+ this.accId;
A single line of CSS should solve all your issues.
This acts in a similar way to position: fixed but will keep the element within your component. But, it still takes up its relative space (which is handy if your table has less the height: 450px; worth of content....
As mentioned in the developer forum post I was able to achieve the above implementation using the lightning component code in this article.
Can you try checking the lightning component code against the above one?
Yes, we can achieve this. We have to do these steps:
Create a LWC/Aura component that can show toast message.
The Aura component will use localStorage to track whether it's first time if yes then we will show the toast and update in localStorage.
And if it's not first time then we simply skip the toast message.
This component will not have any UI elements.