Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 20 Apr 2024 03:16:26 +0000
New Spreadsheets INDEX function
View Count: 1487
| [2014-11-20 06:01:26] |
| Sawtooth - Posts: 3976 |
|
This simple formula for an SMA doesn't work in the new spreadsheets: =AVERAGE(E3:INDEX(E3:E1002,$K$1,1)) Do you have plans to make the INDEX function work as it does in the Old Spreadsheets version? Date Time Of Last Edit: 2014-11-20 06:02:06
|
 New Spreadsheets SMA.PNG / V - Attached On 2014-11-20 06:01:14 UTC - Size: 33.08 KB - 302 views |
| [2014-11-20 18:43:20] |
| |
|
This is true, this will not work properly. A cell range reference cannot consist partially of a direct cell reference and the return value from a formula. There are no plans at this time to support it due to the complexity and we would not put reliance on it ever being supported. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-11-23 23:01:37
|
| [2014-11-21 14:25:30] |
| Sawtooth - Posts: 3976 |
|
This is disappointing. I extensively use INDEX in this way. I offered a simple formula as an example. [There is another way to do it that works:=AVERAGE(OFFSET(E3,0,0,$K$1,1))] But more complex uses of INDEX cannot be easily replicated with other functions, if at all. I also use the INDEX,MATCH combination extensively, like this simple example: =INDEX(E3:E1002,MATCH(K3-1,K3:K1002,-1),1) =MATCH(K3-1,K3:K1002,-1) works by itself, so it seems to be an issue with INDEX. Why does the INDEX,MATCH combination give a #REF! error in scss but not in scwbf? |
| [2014-11-21 18:26:29] |
| |
|
I also use the INDEX,MATCH combination extensively, like this simple example: =INDEX(E3:E1002,MATCH(K3-1,K3:K1002,-1),1) =MATCH(K3-1,K3:K1002,-1) works by itself, so it seems to be an issue with INDEX. Why does the INDEX,MATCH combination give a #REF! error in scss but not in scwbf? Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-11-22 20:53:40] |
| |
|
This is disappointing. I extensively use INDEX in this way.
Provide us a simple example explanation which demonstrates a case which cannot be done due to this limitation. We would think it should not be difficult for us to implement another function to accomplish what you want.I offered a simple formula as an example. [There is another way to do it that works:=AVERAGE(OFFSET(E3,0,0,$K$1,1))] But more complex uses of INDEX cannot be easily replicated with other functions, if at all. You are used to doing things a certain way with the Old Spreadsheets based upon how those were designed. With the New Spreadsheets, there needs to be a new look at how to do things. If there is something you cannot do with New Spreadsheets, provide us a simple explanation of it that fits within the concept of spreadsheets, and we will see how to implement it within the general Spreadsheet framework. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-11-22 21:04:24
|
| [2014-11-23 03:56:35] |
| Sawtooth - Posts: 3976 |
|
Yes, I am used to doing things a certain way, which happens to be the same way the rest of the world uses Excel-compatible spreadsheets. Now I must reinvent the wheel, re-engineering things that are not directly convertible. As I do some reconfiguring, I'm finding other issues, for which I will start individual threads. I just recently discovered that I can use OFFSET to find a moving range as I formerly did with INDEX, so those have been resolved. But please fix INDEX so that it will accept a Row input other than 1, and one from a cell reference, and one from another function. Once INDEX is fixed, will I be able to do this?: MAX(INDEX(MATCH)):INDEX(MATCH))) where I define the range of MAX using a pair of INDEX(MATCH)). |
| [2014-11-23 23:00:46] |
| |
|
The INDEX function had a bug where the row and column offset parameters were switched around. This will be fixed in the next release coming out in a couple of days. Yes, I am used to doing things a certain way, which happens to be the same way the rest of the world uses Excel-compatible spreadsheets. Now I must reinvent the wheel, re-engineering things that are not directly convertible.
The way that the world uses Excel compatible spreadsheets in certain kinds of ways is not necessarily the optimal way. We want to create a more optimal way. There is no doubt there are roundabout ways of doing things which could be a whole lot more efficient with dedicated functions to accomplish the same task. Once INDEX is fixed, will I be able to do this?: MAX(INDEX(MATCH)):INDEX(MATCH))) Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-11-23 23:01:00
|
To post a message in this thread, you need to log in with your Sierra Chart account: