Salesforce CPQ Package Expiration

pavanhnk2022 · July 13, 2022, 04:59

I have install salesforce CPQ package in my DEV org and it shows the expiration date as "Does not Expire". Does this mean Salesforce is supporting CPQ package for life time in Developer Edition orgs? I did not find any link/article regarding the same.

pavanhnk2022 · July 13, 2022, 05:04

Currently, ILogger.LogError() cannot log exception details (e.g stack trace) to local console and azure console, except exception messages. In other words, exception messages appear on both consoles, with no stack trace.

Please note that other type of loggings, e.g. information, is working.

please see below:

ILogger.LogError not logging exception details

There is no response from Azure Function team from below:

https://github.com/Azure/azure-funct...st/issues/6476

Does anyone know the roadmap for ILoggerr.LogError()?

Will it be fixed, or whether it is being replaced by TelemetryClient()? TelemetryClient is still different from ILogger

https://docs.microsoft.com/en-us/asp...-5.0#log-level

https://docs.microsoft.com/en-us/azu...shoot-diagnost

July 13, 2022, 04:59	Salesforce CPQ Package Expiration	#1
pavanhnk2022 New Member hnk Join Date: Jul 2022 Posts: 2 Rep Power: 0	I have install salesforce CPQ package in my DEV org and it shows the expiration date as "Does not Expire". Does this mean Salesforce is supporting CPQ package for life time in Developer Edition orgs? I did not find any link/article regarding the same. Last edited by pavanhnk2022; July 16, 2022 at 03:00.

July 13, 2022, 05:04	ILogger.LogError() unable to log exception details, is it being replaced by Telemetry	#2
pavanhnk2022 New Member hnk Join Date: Jul 2022 Posts: 2 Rep Power: 0	Currently, ILogger.LogError() cannot log exception details (e.g stack trace) to local console and azure console, except exception messages. In other words, exception messages appear on both consoles, with no stack trace. Please note that other type of loggings, e.g. information, is working. please see below: ILogger.LogError not logging exception details There is no response from Azure Function team from below: https://github.com/Azure/azure-funct...st/issues/6476 Does anyone know the roadmap for ILoggerr.LogError()? Will it be fixed, or whether it is being replaced by TelemetryClient()? TelemetryClient is still different from ILogger https://docs.microsoft.com/en-us/asp...-5.0#log-level https://docs.microsoft.com/en-us/azu...shoot-diagnost Last edited by pavanhnk2022; July 20, 2022 at 09:44.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[foam-extend.org] foam-extend-4.1 cannot compile on Centos8	Ya_Squall2010	OpenFOAM Installation	2	July 22, 2020 02:03
[foam-extend.org] paraview not runing? (foam extended 3.2 and ubuntu 15.04)	Milan2013	OpenFOAM Installation	23	April 20, 2017 05:49
[OpenFOAM.org] Building OpenFOAM 3.0.1 on Ubuntu 16.04 - failed	erico	OpenFOAM Installation	30	February 2, 2017 09:24
OF 1.6 ext on Ubuntu 12.10 (64 bit) compilation errors	dreamilam	OpenFOAM Installation	7	April 21, 2013 05:43
Errors running allwmake in OpenFOAM141dev with WM_COMPILE_OPTION%3ddebug	unoder	OpenFOAM Installation	11	January 30, 2008 20:30