collection shows summary of endpoints rather than just end points, where is the setting to change?
i want to see all end points which are easy to locate, but for me after importing api in postman all i see is sumamry for each end point. really hard to lcoate the desired one . please help if there is any setting to change that
hi there, guys!

[@mitrpathak](/u/mitrpathak) i think i get your point.

it’s about naming requests. the way that postman determines how the requests inside the generated collection will be named after importing.

if i get that right, when you are importing a new api into postman, you will find a collapsed panel “sh…
hello, thank you so much for you assistance i have tried in soapui and it was working properly.

in the postman, i was able to get the items added into the queue after adding all the default settings of it.

[image]

now it is working fine.

regards, hi @jcarneiro!great question. if your goals were from a previous quarter, you’ll need to change your view from ‘current quarter’ to the quarter in which those goals were listed.the ‘current quarter’ view should show you all goals (regardless of status) in the current quarter, as well as any other incomplete goals from previous quarters. completed goals from previous quarters can only be viewed in that quarter.here’s a screenshot in case this helps:let us know if you have any other questions! thanks! its kind difficult to understand in my POV but not impossible  

imagining it while reading


can you show some codes? or samples on what you want to achive? if i get this right you are trying to sweep1 circle and have the sweeps come to a point.

if that be the case, you either need to have the sweep paths cross and go far enough past each other to come to a point (at right) or you can place the cross section on the inside of the sweep path rather than … hello [@scotttpa](/u/scotttpa),

for cumulative totals instead of selecting “all” replace it with “allselected” and also replace the ‘recurring subscriptions’[subscription start date]) with the dates table. so your code should be like this overall -

abcs cumulative started to date =

calculate ( [abc order count … <https://docs.glideapps.com/all/reference/components/lists/inline-list#only-show-a-few-items> as i had the time, thought i would tidy things up, just one custom query needed, no view required. just change the office names and copy/paste into a custom query 
have a great christmas party! 
select sum(office1) as office1,sum(office2) as office2,sum(office3) as office3,hours from 
((select 
cou… sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: The existing solutions based on `findall` are fine for non-overlapping matches (and no doubt optimal except maybe for HUGE number of matches), although alternatives such as `sum(1 for m in re.finditer(thepattern, thestring))` (to avoid ever materializing the list when all you care about is the count) are also quite possible. Somewhat idiosyncratic would be using `subn` and ignoring the resulting string...:



```
def countnonoverlappingrematches(pattern, thestring):
  return re.subn(pattern, '', thestring)[1]

```

the only real advantage of this latter idea would come if you only cared to count (say) up to 100 matches; then, `re.subn(pattern, '', thestring, 100)[1]` might be practical (returning 100 whether there are 100 matches, or 1000, or even larger numbers).


Counting **overlapping** matches requires you to write more code, because the built-in functions in question are all focused on NON-overlapping matches. There's also a problem of definition, e.g, with pattern being `'a+'` and thestring being `'aa'`, would you consider this to be just one match, or three (the first `a`, the second one, both of them), or...?


Assuming for example that you want possibly-overlapping matches *starting at distinct spots in the string* (which then would give TWO matches for the example in the previous paragraph):



```
def countoverlappingdistinct(pattern, thestring):
  total = 0
  start = 0
  there = re.compile(pattern)
  while True:
    mo = there.search(thestring, start)
    if mo is None: return total
    total += 1
    start = 1 + mo.start()

```

Note that you do have to compile the pattern into a RE object in this case: function `re.search` does not accept a `start` argument (starting position for the search) the way *method* `search` does, so you'd have to be slicing thestring as you go -- definitely more effort than just having the next search start at the next possible distinct starting point, which is what I'm doing in this function. take a look at the menu starter project for a proper menu structure.

ionic start myapp menu

a menu should exist at a root point, and not be included in multiple pages.