You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some issues renaming and during the investigation i tried to analyse and found out that the data of the diffrent api calls don't match. At the moment i'm sure it is not a "caching" issue. If tested running a powershell against the api se at the end of this text. My test was:
Get the tags using the /v1/tags/get url
Tag: SharePoint = Count: 268
Tag: Development = Count: 118
Get the posts for both tags using the /v1/posts/all?tag=NAME url and count the returned xml nodes
Posts: SharePoint = Count: 266
Posts: Development = Count: 100
Why are the numbers so different? I have about 10 or 15 tags showing this behaviour?
Are you able to identify the links that are variable? There may be difference between how tags are parsed with spaces and commas, depending on when they were entered (before 3 years ago, or more recently when comma-separated tags were introduced.)
I've tried to analyses but on my side I don't get any further. The TAGS api is only getting an count and not the actual posts. All other methods (using posts ALL and posts ALL using the tag filter) will give me a consistent count for the specific tag. Only the TAGS api will show different data as explained in my issue. Is it possible to have a look at my data from the "data" point of view?
I have some issues renaming and during the investigation i tried to analyse and found out that the data of the diffrent api calls don't match. At the moment i'm sure it is not a "caching" issue. If tested running a powershell against the api se at the end of this text. My test was:
Why are the numbers so different? I have about 10 or 15 tags showing this behaviour?
PowerShell 4.0 (Win 8)
The text was updated successfully, but these errors were encountered: