Tabulator issues with update huge dataset - tabulator

I am using tabulator updateData functions to update the data on each interval for huge dataset say (20k records).
After some time the browser become unresponsive.
It was working properly if I have used replaceData function without any issue. I need to use updateData function to retain column checkbox checked state.
JSFiddle - https://jsfiddle.net/0z9xhujt/8/
Browser - chrome,
Operating System- windows
Please let me know if I have missed something

Related

using PXDatabase.Delete to remove all row in a Custom table

I am trying to use PXDatabase.Delete to remove specific row(s) in a Custom table or even just to get it to fire off. Here is the code that I am trying to get running:
PXDatabase.Delete<SSINHoldRule>(
new PXDataFieldRestrict<SSINHoldRule.inventoryID>(18));
When I watch SQL profiler for this code to get executed, nothing shows up in the SQL profiler which means that this code is not hitting the database. I have different variations of the above code but to avail. Any help would be appreciated. I am running this code via the TestSDK.
Generally, this would be considered direct DB manipulation, which is frowned upon by Acumatica (Documented within Acumatica certification guidelines) and should be used as a last resort. Is there a reason this is not working with general DAC record manipulation? We want to assess using that before considering a more brute force methods such as PXDatabase.Delete.

Need advice on loading and saving data on tabulator

I want to load data from a table in my DB using PHP.
+ I want to then edit the data and save it back to the table.
I can't seem to find any examples.
The examples load data that is hard coded in the HTML.
I see there is code to add rows and edit - but I see nothing for saving.
I'm hoping someone can help and give me some pointers.
(Apologies in advance if the information is there - I've looked and can't see - it's 2am and I'm not thinking straight!)
Thanks.
There is an example for loading data into a Tabulator table via ajax here
As for saving it back that depends entirely on how you handle things server side.
you can use the getData function on the table to retrieve an array of data from the table
var data = table.getData();
you would then make an ajax request to pass this data back to the server, it would then be up to you how you go about saving this to the database,there are as many ways to do this as there are backend frameworks so it would depend on what you are already using

SSRS with Report Viewer issues not refreshing

Hi i wonder if anyone can help me, I am absolutely stuck on this one. I will start from the beginning so you understand what I am trying to accomplish.
I have a web page which displays total figures in a grid, below the grid I have a Report Viewer which displays these figures as a line graph via an SSRS report on the server. Recent requirements would like the grid to be filterable, so if they want to see totals for a specific customer or product. While I have this working I would also like the SSRS report within the report viewer to also so the same information.
Now I have this semi working, I have made the necessary changes to the report on the server and this is working correctly, next was to hook that all up with the Report Viewer. I also have this working to a degree. Basically what is happening is if the Async is flase then the report does not refresh even ater telling it to. If I turn Async on it works as expected on my computer with IIS7 however when I upload this to our server with IIS6 after the initial load, when a postback happens or when I try to filter the grid I just get a blank screen. Its like the report is not being displayed.
Any help would be appreciated as I have previously used SSRS with report viewer to get a different report based on option buttons which works, but this does not seem to on the server. Locally it is fine but not where it needs to be.
Give it a try . Set enable 32 bit to true
Below is how you do it from IIS7 manager:
1 Right click on the Application Pool and select “Advanced Settings…” or select the same from the Actions pane after selecting the Application pool.
2 Change the “Enable 32-bit Applications” to True (if you want the application pool to spawn in a 32-bit mode)
3 Click OK.
Ok so I figured it out and while it has taken me a while to get the time to post it on here, I thought I should, just in-case someone else comes across this issue.
So Async ="true" the report is displayed in the report viewer for the first time after any postback occurs I am left with a blank screen. If I turn Async = "false" then I get the report the first time but the report never refreshes. After fiddling for a while it got me thinking if it works the first time then that is all I need and just pass different parameters to the report. So I set Async = "false" and had a look as to how to completely reset the report viewer control. Turns out all I needed was ReportViwerControl.Reset(). This reset the control to its default like almost like we are using it for the first time. Then I apply the report details and parameters and hey presto the report works as expected and the report changes every time a filter is set.
I uploaded this to the server and it is working as expected. Quite why it wouldn't before I am unsure however, i do have to stress that the server is old and has old technology, the reason for IIS6. While our test server and my local copy have the latest technology.
Thank you all very much for your help.

kentico product options not adjusting prices when choosing different options

I am using the RandomProducts web part, and for some reason product options have no effect on the price even though I have added the price adjustments for each variant. Is this normal? I assumed this would work out of the box since its a default option but maybe I have to write my own code... just seems odd. Does something need to be enabled for product options to update the price of a product?
Are you sure you are not having an JS issues on your page? When using the Product Options, you define the option and any adjustment to the price. You then choose the products to apply the option to. When a user selects a specific option, there is a postback that occurs that updates the displayed price. If using the CartItemSelector web part, it will contain all of the postback JS needed to update the price within itself.
This works on a basic demo site so I suspect there is a JS issue that is causing the postback to not complete properly.
Another possible cause could be latency when posting the value back. If it is the first time you are running the site, it's possible the postback is taking longer than expected (due to recompilation) and it is appearing as if it's failing.
Other things to check:
On the Product Options General Tab
- Is "Enabled" checked?
- Is "Display price adjustments" checked?
I'd recommend to check the following things:
JavaScript errors via the developer tools of your browser
Caching settings/expiration for the web part or page
Enable SQL debug (Settings > System > Debug > Display on live site) and check which queries are executed to see where the price comes from

Cognos 8.3 No Data Content issues

Upgrading from 8.2 to 8.3 and testing out the new No Data Content functionality. Report looks in order if results are returned. The No Data message does not appear. However if we test the report (pass in parameters expecting no results), we are returned a blank page (pdf, html, excel output). Not even the header or footer appear on the page. And the No Data Content message does not appear as well.
We have very complex reports using Oracle SQL and in most cases the Header content is linked to a SQL statement to render output from the database as well as list the parameters passed in. The issue seems to be related to embedded data objects, i.e. we have a list object embedded within a table object. I've tried stripping out the extra layers with no success thus far.
In 8.2 we used style variables, i.e. RowNumber()=0 or RowNumber() is null to conditionally hide data objects in the body of the report. We've never used any conditions to hide or display the header or the footer and in 8.3 now this seems to be an issue.
This seemed like such a useful enhancement in 8.3 but we haven't gotten it working yet. Any thoughts or suggestions to try?
Thanks for reading this. I appreciate any advice.
Joe
We ran into this same problem when upgrading reports from 8.2 => 8.4. We reported it to Cognos as a bug -- Not sure if they've assigned a bug tracker id to it, but we got the impression it wasn't going to be fixed soon. (Obviously, if it exists in 8.3 and it has been carried forward to the next version, it's not a high priority.)
I'm sorry I don't have an answer at the moment on how to fix it, but I was planning to look into work arounds next week. I'll edit this post with any ideas I come up with.
UPDATE:
Not sure if this is an available feature of 8.3, but in 8.4 there is a new "No Data Contents" property for data containers (lists, blocks, etc.). Setting this value to yes creates two tabs at the top of the page, one for a page to be displayed if data is returned, and another for instances when no records are found. You can customize a message to be displayed using that second page. Pretty cool, actually, but buried in the documentation.
Hope that helps. If you still have problems, check out the Index topic "no data > specify what appears for a data container."
yea it appears that a blank pdf is returned... but in fact the cognos viewer bugs out at the second prompt page if there is no data. Headers and footers and items in which didnt need data to render ... as not showing up as well.
This existed in 8.2 and we were always able to do some sort of work around to get it to atleast show. Seems much more prevalent in 8.3 now.
Id like a solution on this as well! halp! >_<
Edit: seems a slight work around is to create a new report in 8.3 and copy each component starting with queries... then variables.. then objects on the page.. followed by page sets and master detail relationships. in that order for simplicity. Essentially recreating the report from scratch in 8.3 seems to fix the problem.
This works for about 90% of our reports.

Resources