Search results by user ID 6837

Re: Shared Value not correct after some actions

clayton — Thu, 17 Dec 2015 05:21:49 GMT

Hi Alex

I believe your problem has to do with the shared result cookie reaching its max memory size. Once that happens, everything goes a little wonkey. Some things work, some things dont, NOTHING makes sense... you try tracking down the problem, create new problems, then all of a sudden the original problem is fixed. I struggled with this for a long time - will leave it at that for now [;)].

If this in fact is the cause of your issues, then your solution of switching from one browser to another makes sense, since the new browser shared result cookie was presumbley not all 'used up'.

My current work around is to clear the cookie manually when I think I might be reaching its limit (limit varries per browser). You can do this through the developer console. In Chrome,:

1. Open up the developer console

2. Click on the 'Resources' tab

3. Click on the 'Cookies' link in the side bar

4. Under the 'Cookies' link click the 'www.methodintegration.com' link

5. You should then see a cookie with the name 'YourAppsName.MethodActionSharedValues'

6. You can check the size of the cookie in the column labled 'size' and delete it if need be

I understand that this solution is not optimal/scalable/etc. What I would suggest is reworking your screen(s), replacing all shared results with hidden fields. If you need to pass a value to another screen, use the active record ID if possible. In the cases where you need to use a shared result, I would make use of XML. Each former shared result can be represented as an XML node and all the nodes can be packaged into one string using the character function action and then the resulting value can be set to one shared results value, preferably a value that can be reused on every screen (ie: Alexs_SharedResults).

To unpack the XML you can use the Character Function action >> Get Node Value From XML.

Another issue you may run into when converting from shared results to hidden fields is calling action sets within loops. Since you are not able to update a field within a loop, you will need to build your list of values (ie: table PKs) before calling the action set, set the hidden field value to your list of values, then within the action set you are calling use the 'build selection list' in the 'start loop through table' action to loop over the list of values in the hidden field.

Thanks

Clayton

Possible Platform Issue - Link in grid not working possibly caused by JS errors

clayton — Sat, 21 Nov 2015 03:08:10 GMT

I have a screen with a number of grids - each grid contains a link which when clicked, triggers an action set. Everything was working last night but now when I click the links, nothing happens. I brought up the JS console and it appears that a function tied to the action of clicking a link within my grids causes a JS error - ```Uncaught SyntaxError: Unexpected token ILLEGAL```. See below screen shot (Chrome Version 46.0.2490.71 ).

Additionally, when I publish the screen and get the front end prompt to refresh my screen, I am not able to and get an error in the console reading: ``` Uncaught TypeError: Cannot read property 'parentNode' of null ```.

I have tried on different browsers (including hard refreshes and logging in and out from different accounts), mac and windows, on my computer and remote computers, and in all scenarios get the same error. I have not noticed errors on other screens... so think it is limited to this one screen. Additionally, I have created new links in existing grids and entire new grids with no luck.

Problem Customizing Screen - Hidden Sections

clayton — Wed, 01 Apr 2015 01:18:01 GMT

I have a scree with 10 sections and quite a bit of buttons, fields, grids, action sets, etc in each section. Last week I was doing some housekeeping and went to reorganize the sections and the page reloaded and only the first two sections were visable. After some troubleshooting I realized the sections were still there, just hidden within the html (display:none vs display:inline-table; see below image). Also, when navigating to the view of the screen, the sections where visable and all functionality apeared to work as expected. The only odd thing is that each scetion's title was changed to what I am assuming is a default section title placeholder, ie: section1, section2, etc.

At the time, I thought there may be something odd going on with the tabs functionality (the hidden sections were in tabs). The two that were visible were not. I changed the setting - Advanced Screen Properties > Section Layout from 'Show in Tabs ( Tabs start at section 3 )' to 'Show In Sections' - and that did not solve the problem.

I contacted two of your 'Community Support Specialist' and they directed me to this forum.

Also note, there were no errors in the JS console.

I have more screenshots and can direct a method tech to the appropriate screen, but would rather not post that infomration in a semi-public forum.