Skip to Content

[FEEDBACK] Tag not available: SAP Business One SDK

Questions pertaining to the use of the SAP Business One SDK can no longer be tagged with the tag "SAP Business One SDK". This is however the tag that all the SDK experts know and follow.

Apparently you should now use the tag "SAP Business One Extensibility". Problem is, no one has heard of this tag, so the relevant experts do not know it exists and/or do not follow it.

I am sure there was a perfectly good business politically correct reason for depricating the tag, with the common sense name, that everyone knew and was using, and replace it with a tag that makes no sense.

So would it be possible for SAP to solve this problem by either (in this order of preferability):

  1. reversing this poor decision
  2. by merging the SDK and Extensibility tags
  3. by mapping the SDK tag to the Extensibility tag
  4. specifically informing users of this poor decision by message or email.

If the idea was to reduce the number of tags, maybe it will help to instead delete / depricate and/or merge unknown and mostly useless tags like:

  • "SAP Business One, version for HANA"
  • "SAP Business One, version for SAP HANA" (because, why have only one tag for HANA?)
  • "SAP Business One Cloud"
  • "the intercompany integration solution for SAP Business One" (seriously, does anyone ever search by this tag?)

because any questions that SAP would like users to tag with these tags, are already tagged with the normal "SAP Business One" tag.

I cannot help but think that the development of the new SCN is so slow, because all SAP's resources are being spent on solving problems that they first created themselves.

Add comment
10|10000 characters needed characters exceeded

  • I would ask Peter Hartwich to help explain the reasons for why we created the SAP Business One Extensibility to replace the SDK tag.

    I can say that we plan to merge the SDK content into the Extensibility topic when we transition to the new community topic structure, but unfortunately we couldn't do it at the time the Extensibility tag was created.

  • Allright, if the SDK tag is going to disappear entirely, and be replaced by Extensibility, then maybe it is not such a terribly poor decision.

    Will there be a redirect of links with the SDK tag?

  • Yes. You can test this even now by changing the primary tag on a piece of content and checking the URL.

    When we move to a new experience, essentially all the content will be "moved" in some sense, because the structure is new. Even content that has the primary tag SAP Business One will need to go to the SAP Business One topic area, and I can imagine the URL structure might be slightly different. And in some cases, like this one, you might have a tag that moves to something totally different.

    (You can see from another discussion that I had been retagging some content in advance of any new topic structure being release, just to get a head start. But the point is that when we do make a switch, we'll want to map some of the wrongly-tagged content to proper homes. So a lot of content will move.)

    No matter how "far" a piece of content moves, we'll make sure the path to a piece of content isn't broken. But worth me following up on what, if anything, happens to URLs of individual pieces of content in the new structure.

  • Get RSS Feed

1 Answer

  • Best Answer
    May 30, 2018 at 05:52 AM

    Please check the following blog for details on the changes:


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Peter,

      As I said, to me it makes it seem like that. It is simply a matter pf perception. I am sure that it is not actually the case.

      I see no point in further discussing this matter. I see your point, and if a similar situation arises in future, I hope you'll consider mine.