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.
Related
I applied this notification without knowing what it does. Now UI is missing. It says "Some issues were found while trying to render this preview" while preview and when I run app, It shows a blank surface. How and Where can I configure this?
Finally I find what the notification changes in the project.
when I apllied notificitaion , it adds build.gradle:app to this twice like below.
implementation 'androidx.core:core-ktx:+'
implementation 'androidx.core:core-ktx:+'
Although I have already implemented this
'androidx.core:core-ktx:1.9.0'
This leads rendering problem.
For my Android Buildfire app, I am using buildfire.history to navigate between screens within my plugin. Using the Buildfire built-in back button in the title bar works fine and correctly pops the history when pressed. However, when Android's native back button is pressed, it does not pop the history and instead seems to want to exit the plugin (which is especially a problem on the home screen as it exits the app no matter how many breadcrumbs have been pushed).
I would expect this to work the exact same as the built-in back button. Is this a bug in buildfire? I even made a super simple plugin to test the history navigation and it is an issue.
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!
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.
I added a couple of custom control into a plugin and imported them on the server using the update site. They are working quit well so far but when i open an application in the designer client i can see the custom control from the plugin twice.
I tried to add them the same way bootstrap4xpages is adding a plugin but mine is duplicated.
One entry is without any icon the other has the standard grey cc icon. Not the end of the world but i must have done something wrong. Any idea why that happens?
It's a known issue with 9.0 and 9.0.1, specific to components that are Custom Controls. I encountered it quite a while ago. Mark Leusink had the same problem for Debug Toolbar and discussed it with the IBM developers at IBM Connect last year. So I would hope it will be addressed in the next point release, 9.0.2.
It still works fine though, regardless of which one you select.