I'm using webdirect to access fm database pages. Here, I have some problem which is constantly refreshing the screen.
I'm thinking to stop this and should not be refresh anymore. Can someone share your ideas to prevent this ?
Are you on FileMaker 14?
Yes Mike.. I'm using FM 14
Do you have triggers? timer scripts? any other obvious stuff that would slow down or cause refreshes?
Also, describe your refresh, is it blinking, are you getting a spinning wheel?
Go directly to this video about how to design for webdirect.
Do not pass GO, Do not collect 200$.
Thanks for your reply mike
I'm not using any triggers and getting spinning wheel most of the time and some time blinking.
I'm not using many objects on the layouts. Its very simple to show 20 records with 4 columns in table view.
I had a similar problem. These were caused by old layout objects which I 'parked' in the hidden area of the specific layout.I expected these would be inactive, skipped in updates. But in fact they are still being refreshed and updated.That update of not only the portals in sight but also the portal in the hidden part of the layout caused the repeated blinking of the layout.
Else, backup the file and start deleting 50% of the objects in the layout until you identify the field causing the problem.
Table view is unsupported in webdirect?
do you have a looping script running in the background?If so, and if that script updates a field which is also on the layout the layout will refresh as well.
Can anyone guide me how to get rid from the refreshing issue. I have updated the Filemaker Server version to 14.0.4 form the guidance of Filemaker Support team but still getting spinning wheel with white background for each of the click.
Thanks in Advance.
That sounds like your server or network is too slow, or you have triggers that are running after each click.
Also post a new question instead of resurrecting an old one from four months ago.
Thank you all for your response,
Still the issue is not resolved with the updated versions.
I'm dam sure that I'm strictly following recommended things when I develop weddirect pages. but still I have refreshing issue.
Regardless of development, if your server or network connection is underpowered, you will see issues.
Thanks Mike, Its make sense.
But looking forward we have to find the way to fix this issue, as I can see many discussions and many customers are in trouble of this
You keep saying it's an issue, but like I noted it probably isn't filemaker's fault. I have more than a few solutions on webdirect live in production without a lag or refresh issue like you say you have, so I'm a bit skeptical that you have done everything possible to optimize your hardware, network, and solution.
You haven't posted any specifications on what your server is like, or what the network connection is like between the server and host you are seeing problems on.
Does your application experience similar flickering as in the video in the discussion hereunder?
Re: What can make FM14 webdirect screens stop flickering?
I sent a copy of the file to TSGAL.They could reproduce the problem.Their developers are investigating the issue since 6 weeks or so.It has been quiet ever since.Maybe they burried the issue and hope we forget about it .....
Your solution revolves heavily around portals on almost every layout. FMS14 has a documented speed improvement of 25% over 13, so I wonder if you've even recreated the video under 14 to see if your behavior improves?
Have you tried switching to list and form views instead of relying on portals? There were a number of single-portal layouts I saw that could easily be converted. I rarely (if ever) use portals in webdirect given their nature (a scrollable section inside of a scrollable window). Note that in your video at :03 when you go to a form view, there is no double flash, it just loads. All other layouts you show use portals.
Another tip, if you have non-editable field values (something you don't want to be able to edit in browse mode), turn it into a merge text field. Each "field" is actually a responsive form that has a large chunk of code on it's own. Merge text is treated more as a plain text box, so it loads much quicker than fields.
If I have to use a portal, I regularly do not allow editing in it for the above reason. I only show merge text in the portal, and give an edit button to either edit that row in a popover, or on a separate layout. I've found this the best performing setup for WebDirect.
The flash you're seeing looks like it's loading the portal object first, and then the full content of the fields inside of the portal. This could be a result of browsers drawing objects before they've received all of the instructions from the server, which may not be something FMI can control with the products they are using to render layouts (VAADIN).
Lastly, how customized is your theme? Are you using one of the themes that came out in FM13, with no extra styling on your portal? Remember that custom CSS/design adds "weight" to your load time, so the less styling you do from a filemaker base theme, the faster it is.
thanks for your extensive answer.The video you see, is our application in FM14.It was a 100% IWP application that worked great in FM12.
The theme is indeed customized, but nothing special, no heavy pictures, just some special lines or field sizes.Filemaker can't expect developers to only use Filemaker themes.
The fields in the portals are all not editable and show stored values only.
The phenomenon occurs in every layout, also layout without portals.
The bandwith of connections should not be the problem.The dedicated server has a guaranteed 1 Gbps connection at server side and we have 100 Mbps connections at client side.
More important: the flickering is worst in Google Chrome recent versions.It is less or a bit more acceptable - still not OK though - in IE11 and Microsoft Edge.It has to do with browsers loading layouts first, then rendering those layouts and then loading data into the rendered layouts.I am quite convinced that this isn't an application issue, it definitely seems to be a technical Filemaker Webdirect issue.
have you tried switching to merge text? based on what I saw using that instead of fields (which aren't editable anyways), will save you thousands of lines of rendered code. Even if the field can't be changed, it still renders the field object, which is a lot more lines than the text object. Multiple that by the number of fields you have, and the number of rows you're showing, and that's thousands of lines of code.
Play around with that and see if there's any change. My next recommendation would be to consider list views.
Thanks for your input in this discussion. I am still convinced that this is a Filemaker fault.I followed your suggestion and switched all fields to merge text. No difference.Then I removed all fields from that layout except for 4 merge text field. See the video.Even with only 3 or 4 merge text fields, this layout is already showing the flickering as you can see.This is Chrome 47.0.2526.106, the latest version you can get in december 2015!
It has been quiet for weeks now after I uploaded my solution to TSGAL.TSGAL Could reproduce the problem, so I guess Filemaker has no solution for this.And that is really a problem.Because we developers can't sell solutions if layouts containing more than 2 fields behave like pinball machines!
Filemaker can you update us on this, please?
The issue is still only happening on your portals, so I stick with my suggestion to use list views and limit portals as much as possible. Also, in this second video, it seems that the "smoothness" was improved over the first one for most of the times you click back to the layout with two portals.
What does the green outline of the field indicate, is that conditional formatting?
PS - I agree that FileMaker should chime in here, but I'm still debating that this may be a non-issue and just the way that WebDirect works. I know you mentioned you converted from an IWP solution, but WebDirect is completely different in form and function.
Thanks for your response. The second layout has no portals at all, only 4 merge text fields and even there you can see the flickering.
I think it is logical that rendering time increases if a layout holds more objects.But if a layout has only 4 merge text, we don't want to see any flickering at all.U
We have tried list views but they bring their own design restrictions.
I know that IWP is very different from WebDirect.But we and our users were really happy with IWP.I my view Filemaker presented us, developers, with a serious problem by introducing this immature WebDirect technology too early.
What is the OS version of your FileMaker Server? We have struggled with this issue as well, but recently saw a substantial decrease in the WebDirect spinning wheels on systems hosted on Windows Server 2012 R2, rather than Server 2008.
this application runs on a dedicated Windows 2012 R2 server which is 100% configured according to Filemaker specs
Retrieving data ...