Is there a way to have multiple custom functions with different namespaces?

[wh1t3cAt1k]

As I understand it would require setting up several extension points with type CustomFunctions, each of which would have a separate namespace.

Is it supported?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 94ad7803-d4f7-a700-7c7f-204cd8f34e4a
• Version Independent ID: 9c485bae-cab1-bdad-4c8e-baad2b12b22d
• Content: Create custom functions in Excel - Office Add-ins
• Content Source: docs/excel/custom-functions-overview.md
• Product: excel
• Technology: add-ins
• GitHub Login: @o365devx
• Microsoft Alias: o365devx

[mscharlock]

Hi @wh1t3cAt1k - I am going to transfer this to the Excel-Custom-Functions repository, where we can check with an engineer (I am just not sure on the answer on this one). Thanks!

[mscharlock]

@RuoyingLiang - Do you mind answering this one? I think this is possible but I want to check.

[RuoyingLiang]

@wh1t3cAt1k Custom function in one add-in don't support different namespace. Could you share with us your scenario to help us understand the requirement?

[mscharlock]

@RuoyingLiang - I will go ahead and make sure this is accurate in the docs! :)

[wh1t3cAt1k]

@wh1t3cAt1k Custom function in one add-in don't support different namespace. Could you share with us your scenario to help us understand the requirement?

@RuoyingLiang the scenario is rather simple. We connect to back ends of different providers that expose their public APIs to us, but with similar functionalities, e.g. CalculateInterest().

We need to disambiguate clearly between providers in the naming. Currently we are only able this through prefixing:

CONTOSO.FOOCALCULATEINTEREST()
CONTOSO.BARCALCULATEINTEREST()

etc.

Would be a bit nicer to say CONTOSOFOO.CALCULATEINTEREST() and CONTOSOBAR.CALCULATEINTEREST().

Basically that is our scenario.

[wh1t3cAt1k]

Nested namespaces like CONTOSO.FOO.CALCULATEINTEREST() would rock even more in terms of readability and intuitiveness.

[akrantz]

The name of the custom function can have a prefix, so instead of the function being CALCULATEINTEREST(), the actual function name can have a period and be FOO.CALCULATEINTEREST() and BAR.CALCULATEINTEREST(). If you have the namespace as "CONTOSO", then these would appear as CONTOSO.FOO.CALCULATEINTEREST() and CONTOSO.BAR.CALCULATEINTEREST().

[wh1t3cAt1k]

Thank you. This works for us.

@akrantz will this require calling CustomFunctions.associate? I trust JS functions cannot contain dotted identifiers.

Please @mscharlock clarify this in the documentation - maybe including the workaround suggested by @akrantz?

Close the issue yourself when ready please, and thank you again for helping out!

[akrantz]

The JavaScript function name cannot contain the period, but the name in the metadata certainly can. These names do not have to be the same.

I'd like to call out that the Yo Office template for custom functions has a webpack plugin that can generate the custom function metadata from the JavaScript/TypeScript source. It will generate the metadata name from the JavaScript function name but you can override this in the @customfunction tag. We made sure to allow for periods in this name for just this reason. The webpack plugin can also generate the associate calls automatically(). If you want more info about using this, I'd be glad to assist.

Otherwise, you can call associate yourself.

CustomFunctions.associate("FOO.CALCINTEREST", fooCalcInterest);

[wh1t3cAt1k]

Yes, I see that you can also do it using a JSDoc attribute using the plugin you mentioned: ``` /** * @customfunction MY.NAME MY.NAME */ ... ```

…

On Fri, 22 May 2020 at 17:22, Adam Krantz ***@***.***> wrote: The JavaScript function name cannot contain the period, but the name in the metadata certainly can. These names do not have to be the same. I'd like to call out that the Yo Office template for custom functions has a webpack plugin that can generate the custom function metadata from the JavaScript/TypeScript source. It will generate the metadata name from the JavaScript function name but you can override this in the @customfunction tag. We made sure to allow for periods in this name for just this reason. The webpack plugin can also generate the associate calls automatically(). If you want more info about using this, I'd be glad to assist. Otherwise, you can call associate yourself. CustomFunctions.associate("FOO.CALCINTEREST", fooCalcInterest); — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHLV3REVQFFMSGICNHTBCLRS2DBRANCNFSM4M6D3MYQ> .