I'm working on my buildfire app locally. Last night I closed my laptop without any errors. Today, I hit the refresh button and got this error:
Not sure what's wrong. My other apps that I haven't touched in a while are also not working / getting the same error screen. Also, the admin panels still work fine, just not the widget itself. No errors when I go to app.buildfire.com. I even tried pulling the latest sdk but still getting an error.
Nothing in the widget is responsive when I click on it except the "cancel" text. When I click the cancel text another error will appear in the console.
Doing another pull of the SDK fixed the issue.
Related
This is a bit of a weird one:
Attempting to publish a PowerApp to my site however some of the onChange events are not firing after being published. The Preview in the app is working fine, however the version published to the site does not.
I have tried restarting PowerApps, the browser, my computer, republishing after each with no luck. Anyone run into this issue before and have a solution?
Okay - After hours of messing with this I got it to work but the solution doesn't resolve the bug, just gets my desired result.
What I was doing:
Specifically what is happening I am using an onchange event from a dropdown to assist in naming the title of the same list item.
OnChange: UpdateContext({varNewName: "example text"})
However, the title box simply wouldn't update after being published. In the preview mode in the developer environment it was running fine.
I decided to duplicate the box for laughs, tested it, both updated in preview mode just fine.
Published it and the original box was now working, the second box however was now doing nothing. If anyone knows why this is happening I would love to know, it is driving me nuts.
TLDR: If you are having this issue duplicate the recieving end of your trigger and it might resolve. ¯\_(ツ)_/¯
Same issue with rating control.
After a long day, I changed default value of binding source from Blank() to Zero. And it works fine!
I am having a strange issue that I think might be Chrome related but wanted to post here for thoughts.
I have some users who when trying to log into my node.js application, they press enter or the log in button and it just sits and spins and never times out or anything. When looking at the Network tab when this issue occurred the POST never showed up. I then put some alerts on the button click with javascript and as long as the button was in the tag nothing showed up.
Completely deleting the users' profile (suggestion from Google) made it work...until chrome updated and then it happened again.
Using any other browser, no issues. Chrome Beta, the issue shows up. Chrome Canary, I have had 2 users testing for over a week and they have not seen the issue reappear. Incognito has the issue occur as well.
Google Support asked me to send a HAR file to them. The interesting thing was when I opened up developer tools, went to the network tab and then cleared the screen to start a recording, the issue disappeared for that moment only.
It is working for 80% of my users so I can't see how it could be a coding issue, this is also a login that I created over a year ago and have not touched since.
If anyone has any insights I would love to know what might be causing this.
After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.
Not a code question but its stopping me from writing any code. In Azure the maximize button on easy tables is missing in all browsers including Safari, Chrome and Firefox. Also emulating Internet Explorer and Edge in Safari gives the same result. Im on a Mac and don't have access to a windows machine. This button was right next to the close button, now its gone. Has anyone seen this issue or found a fix?
They removed it some time ago (not sure the reasoning behind this, annoying as hell). Nothing you can do about it. Well, you can créate a feedback ítem. thats about it.
I'm using a Windows\Centos laptop, so you can be sure your OS is not the issue.
update:
you can kinda work around it:
I found a fix just now. Grab the right side of the browser window and
drag to the left to make it small. The button appears! If you drag and
make the window larger the button disappears.
I have recently implemented a custom plugin that is just a basic JQuery application. When I'm in the admin dashboard, the back button works perfectly fine, send me back to the previous plugin I just came from. When I view it in the previewer however, the back button does nothing. I never overrode the back button functionality in the actual plugin code, so I'm not sure how this would be happening, especially since the back button functionality is working inconsistently between the dashboard and previewer.
I also tried restoring the back button's default functionality via the SDK navigation methods, as well as setting a custom navigation function on back button click. Neither of those worked. I am not even able to view this plugin in the debugger, as nothing will show up for this particular plugin in the list of remote sources when I try to debug it, so I can't even see if there is some error being thrown. Any ideas?
Do you have the latest version of the SDK? I believe there was a fairly recent release that fixed an issue related to the back button.
I have the latest version of the SDK and the back button works for me in the plugin tester.