TM1 Forum

Hello,

A client has created a spreadsheet. It is running very slowly. It comprises of a number DBRW for data capture. I enter data into a cell and wait 5-10 seconds to enter data into the next cell.

If I have the following which I have tried different scenarios:

Scenario 1: Current set up

I have 4 months of data capture for cashflow through the web. If my rows go over roughly 350 rows. This goes at a snail pace.

Scenario 2: Strip down to just capture one column

I have 1 months of data to capture through the web which still runs slowly.

Scenario 3: Strip the rows to 250 for one month.

I stripped the rows down to 250 for data entry of one month and it flies.

Scenario 4: Strip the rows to 250 for four months.

I stripped the rows down to 250 for data entry of four month and it flies.

What puzzles me it seem to render the rows rather then columns. The less rows I ran the faster it goes rather then the amount of DBRW which I initially thought the problem would be.

Any one experienced this before?

Herman

Interesting......

I split the sheet up into 2 excel sheets. The second sheet worked slowly, but the first part was loading alot faster.

I then took out one account which I had found was not working. It had caused everything to run slower. Once deleted everything worked again.I then added this account back and it seemed to work again much faster.

Least I have a solution......

BTW the server is 9.4 FP2 and Clients are 9.4 FP1

Herman

Herman,

We've seen similar poor performance when rows are numerous in a websheet. Our work around has been to create a process action that reads in a template file that the user uploads to a network share.

Can you clarify your "solution"? When you say an account wasn't working, what do you mean? Did the mere act of adding a second sheet (regardless of how much input content moved to the second sheet) somehow make the first sheet faster?

What's your solution look like now? Are you able to get fast input working with more than 250 rows? Our need is something like 1500 rows by 12 months.

Thanks. -- John

John,

The issue was the following:

My websheet had been working very slow. I took out my input line of a specific account. I then reloaded the sheet back to application and it was much faster then the websheet capture. I then recreated the Excel Sheet with this specific account and upload it back to TM1 Applications and since then I have had no issues.

I think since I had deleted the problem lines and re-created this sheet the issue seem to resolve itself......

Herman