Attempting to use an environment variable to hold several configuration values versus making a separate environment variable for each one for a solution.
The structure (good or bad) is something like below. The issue is when I try to copy this value into the Default box, the Save button is never enabled. I've reviewed the limitations for Environment Variables and this should not drive the solution above 26 MB. I've tried reducing (/s)+ to one and also removing (/n)+ to none before pasting in.
It seems like it would be really tedious to make a separate environment variable for each value when the Parse Json connector could do this fairly easily, am I missing something?
{
Solved! Go to Solution.
A fix has since been put in for this, not sure if the change had anything to do with this post. But this seems to be no long an issue as it has a 2000 char limit now
Although it is not listed in the limitations of this documentation
Use environment variables in solutions - Power Apps | Microsoft Docs
Thinking along the same lines, are there any reserved or special characters that cannot be in an environment variable?
A fix has since been put in for this, not sure if the change had anything to do with this post. But this seems to be no long an issue as it has a 2000 char limit now
Although it is not listed in the limitations of this documentation
Use environment variables in solutions - Power Apps | Microsoft Docs
I have the same issue, my Parse JSON schema is very long, but extremely simple.
I would like to use a Environment variable to store it, just to make it more manageable, but I get the 2000 characters limit error.
I don't understand your response: the issue is that the JSON variable is limited to 2000 characters, how can this "No longer be an issue" when IT IS the issue.
User | Count |
---|---|
16 | |
16 | |
14 | |
9 | |
8 |
User | Count |
---|---|
27 | |
26 | |
24 | |
23 | |
15 |