Why Are Things Still Showing Up As Using JS?
Like some others, I have been working on adjusting a few pieces of our app to accommodate for the new JS usage rules and I have quite a few fields that I thought were fixed as I am now directing the ...
Forum Discussion
Thanks Austin. I do not get the "unsupported code" popup when I open those fields anymore, which is part of the reason I assumed the fields were fixed (and they very well may be).
The Inserted Javascript Usage app was something quickbase released on resources.quickbase.com with the initial announcement about the changes that is supposed to identify areas in your app(s) where unsupported scripting is in use so developers can fix it. From my understanding, it scans your apps weekly and I figured it would no longer display fields once they had been corrected, but I feel like I'm doing a lot of assuming here. That was the main point of my question--I'm just disappointed to have not received the gratification of a smaller number after making changes.
------------------------------
Ryan Huffman
------------------------------
The Inserted Javascript Usage app was something quickbase released on resources.quickbase.com with the initial announcement about the changes that is supposed to identify areas in your app(s) where unsupported scripting is in use so developers can fix it. From my understanding, it scans your apps weekly and I figured it would no longer display fields once they had been corrected, but I feel like I'm doing a lot of assuming here. That was the main point of my question--I'm just disappointed to have not received the gratification of a smaller number after making changes.
------------------------------
Ryan Huffman
------------------------------
Is your app sandboxed? Even without a sandbox created if it is enabled that often prevents things from being done to it. It is the reason I both love and hate the App Library that someone released before. It does not update an app when the sandbox is open because field settings are not accessible.