Content not displaying in published version of App

[Titortian]

All,

Note1: This is the second time I am posting this. The first time for some unknown reason it was flagged as spam which makes no sense, as it if anything could be considered a bug report.

Note2: Sorry for the gaps in formatting I have tried to remove them every way I can but the forum software keeps putting lines in between multiple types of content.
I am having an issue where a variable is not displaying in the published version of my app.
In my work space I am having no issues, in the published version I am.

Work space:

Published:

In the published version the same variable is being used on another screen and is not having any issues:

The '6' is the set variable.
Code excerpts:
Setting of variable.

Set(
    vSANNodeQtyAlpha,
    vSANStartServerQtyEntry
);

Variable: vSANNodeQtyAlpha
'vSANStartServerQtyEntry' is the text entry box on the left in the image.

The next section is:

Set(
    vSANOpticsQtyAlpha,
    vSANNodeQtyAlpha * "4"
);

This is also important as this uses the variable in it and is used on the next sheet which is a copy of the sheet where things are not working but where every reference to 'Node' is replace with 'Server' in naming and declaration.

Use of the variable where it is not working in published version.

"Based on current settings " & vSANNodeQtyAlpha & " servers will be requested."

Secondary Use of variable where it is not working in published version.

"Please provide quote based on attached BoM for " & vSANNodeQtyAlpha & " Servers. Please use the " & !!!variableomittedforclientconfidentiality!!! & " sheet."

Use case of variable where it IS working in published version.

"You have set " & vSANNodeQtyAlpha & " Servers, please proceed."

Example of next sheet where the same use case is in play with the derived variable.

"Based on current settings " & vSANOpticsQtyAlpha & " optics will be requested."

Picture of this in use:

I have gone through the following also.
Saved --> Publish
Save As (New Name) --> Publish
Publish --> Overwrite
Duplicated Sheet --> Saved --> Publish
None of these have helped.

[digiservice]

Have you tried using .Text so:

Set( vSANStartServerQtyEntry, vSANStartServerQtyEntry.Text);

P.S forums don't like you using too many of the code markup tags this is what is getting your post marked as spam

[Titortian]

I am not sure where I would set that variable.
I tried within the submit button where I am setting my variables for future use but it throws errors indicating:
Unexpected Characters. The formula contains 'Ident' where 'Control' is expected.

I also tried in my output to put vSANNodeQtyAlpha.Text instead of just vSANNodeQtyAlpha and while it does not break anything in the developer environment, it also does not fix anything in production.

Any additional thoughts?

[v-xida-msft · Accepted solution]

Hi @Titortian ,

Do you mean that the global variable (vSANNodeQtyAlpha) does not work in your published app in one screen but work in another screen?

Based on the issue that you mentioned, I think this issue may be related to vSANNodeQtyAlpha initialization within your app. As an fixed solution, please consider remove all vSANNodeQtyAlpha variable setting formulas from your app, then re-set the vSANNodeQtyAlpha variable as below:

Set(vSANNodeQtyAlpha, vSANStartServerQtyEntry.Text)

Note: The vSANStartServerQtyEntry represents the Text Input box itself rather than a Text value. If you execute the Set(vSANNodeQtyAlpha,vSANStartServerQtyEntry) formula, the vSANNodeQtyAlpha variable would be a object value rather than a Text value as below:

and the vSANNodeQtyAlpha object value may not include the entered text value.

Please consider remove all vSANNodeQtyAlpha variable setting formulas within your app, then re-set your vSANNodeQtyAlpha variable using above formula, then re-publish your app, check if the issue is solved. You could consider go to see the vSANNodeQtyAlpha variable value details, then you could find where do you set the vSANNodeQtyAlpha variable:

Best regards,

[Titortian]

Kris,

I will try to change this.
Yes, you are correct in stating that the (vSANNodeQtyAlpha) global variable does not work on one screen but does work on another.

The other item of note  I am using [ Set(vSANOpticsQtyAlpha, vSANNodeQtyAlpha * "4"); ] on the next line in the same submit button.
Where I am having issues with (vSANNodeQtyAlpha) displaying I had copied the page and changed all references to Node and just replaced them with Optics so for instance in the variable set above you can see that one is vSANNode... and the other is vSANOptics...

On the sheet that has the substitution with Optics for Node, the value is showing up with no issues in the published version.

Thank you,

[Titortian]

@v-xida-msft 

This solved my issue with the number not showing up on the published version, and I will mark it as accepted.

Now I have a different issue.
I believe you also assisted with the attachment and flows to an email embedded in a form for me on this same app, but now, after changing to XYZ.text, when I attempt to send the email, it no longer sends and instead has an error.

Set(vSANNodeEmailBodyServer,vSANQuotesServerEmailBodyText.Text);
Set(_emailRecipientString, Concat(MyPeople, Mail & ";"));           
PowerAppsServerBoMEmail.Run(_emailRecipientString,vSANNodeEmailBodyServer);           
Reset(vSANQuotesServerEmailBodyText);        
Clear(MyPeople);
Set(vSANQuotesServerEmailSent, 1)

I tested the flow itself, and it still works just the tie in from PowerApps is having an issue.

[v-xida-msft · Accepted solution]

Hi @Titortian ,

According to the issue that you mentioned, it seems to tell that there is something wrong with the value you provided for the 'Sendanemail(V2)_Body' argument of your PowerAppsServerBoMEmail.Run(...) formula.

On your side, please check if the vSANNodeEmailBodyServer variable is a valid Text string value within your app. Please consider remove the flow connection from your app, then save and re-load your app, then re-create a new connection to your flow, then try your formula again, check if the issue is solved.

In addition, I think it is not necessary to set a variable to store the vSANQuotesServerEmailBodyText, instead, you could consider directly reference it within your PowerAppsServerBoMEmail.Run(...) formula. Please modify your formula as below:

PowerAppsServerBoMEmail.Run(Concat(MyPeople, Mail & ";"), vSANQuotesServerEmailBodyText.Text); // Modify formula here           
Reset(vSANQuotesServerEmailBodyText);        
Clear(MyPeople);
Set(vSANQuotesServerEmailSent, 1)

If the issue still exists, please consider re-create a new flow on your side, then create a connection to the new flow from your app, then try your above formula again, check if the issue is fixed.

If the issue has been solved, please consider go ahead to click "Accept as Solved" to identify this thread has been solved. If you have any other questions about PowerApps, please consider open a new thread within this community.

Best regards,