The current workaround is to run the below script against the companies that you are running the newly created SmartList against as this will give the DYNGRP database role the necessary rights for the functions. Here is the url to download the script from: https://mbs2.microsoft.com/fileexchange/?fileID=6fec21d8-1348-4733-bc64-2028a1f4cf2e
Please watch for this to be fixed in a future service pack.
Downloaded Script:
DECLARE @FuncName varchar(101),@SQLString varchar(500),@SysDatabase varchar(60)
SELECT @SysDatabase= DBNAME FROM SY00100
execute ('DECLARE EnumeratedFunc_Cusror CURSOR FOR
SELECT DISTINCT FUNCNAME FROM '+@SysDatabase+'..SY10997 WHERE Language_ID = 0')
OPEN EnumeratedFunc_Cusror
FETCH NEXT FROM EnumeratedFunc_Cusror INTO @FuncName
WHILE @@FETCH_STATUS = 0
BEGIN
execute('if exists (select * from dbo.sysobjects where id = object_id(N''[dbo].['+ @FuncName+']'') and xtype in (N''FN'',N''IF'',N''TF'')) ' +
'GRANT EXECUTE ON [dbo].['+ @FuncName+'] TO [DYNGRP]')
FETCH NEXT FROM EnumeratedFunc_Cusror INTO @FuncName
END
CLOSE EnumeratedFunc_Cusror
DEALLOCATE EnumeratedFunc_Cusror