@SirTipzy Since you have a method call "DateOnly(...)", Can you share me your configuration about this method into the model?
Otherwise, ODL doesn't know this method?

And, if you can share a repro using a github repository, it can help us to dig more for you. Thanks.

@xuzhg I unfortunately do not have a github repo I can share.

I do not have problems for your OData Library to recognize and use my methods. I would not even get the exception I am getting if it did not know of the method.

Here is my class I use to add my methods. I call the UseCustomODataFunctions at startup

public static class CustomODataFunctionService
{
    public static void UseCustomODataFunctions(this IApplicationBuilder app)
    {
        var methodInfos = typeof(CustomODataFunctions).GetMethods(BindingFlags.Static | BindingFlags.Public);
        foreach (var methodInfo in methodInfos)
        {
            RegisterCustomFunction(methodInfo);
        }          
    }

    private static void RegisterCustomFunction(MethodInfo methodInfo)
    {
        var functionName = methodInfo.Name;
        var returnType = TypeToReference(methodInfo.ReturnType);
        var args = methodInfo.GetParameters()
            .Select(x => TypeToReference(x.ParameterType))
            .ToArray();
        var signature = new FunctionSignatureWithReturnType(returnType, args);
        ODataUriFunctions.AddCustomUriFunction(functionName, signature, methodInfo);
    }

    private static IEdmTypeReference TypeToReference(Type type)
    {
        var underlyingType = Nullable.GetUnderlyingType(type) ?? type;
        var primitiveTypeKind = EdmCoreModel.Instance.GetPrimitiveTypeKind(underlyingType.Name);
        if(underlyingType == typeof(DateTime))
        {
            primitiveTypeKind = EdmPrimitiveTypeKind.DateTimeOffset;
        }
        var isNullable = type.IsClass || Nullable.GetUnderlyingType(type) != null;
        return new EdmPrimitiveTypeReference(
            EdmCoreModel.Instance.GetPrimitiveType(primitiveTypeKind),
            isNullable);
    }
}

I have similar methods that have string parameters. These functions work as they are not explicitly set as nullables. I have also tested with none nullable DateTimes. These work if I change my DateOnly parameter to a normal DateTime. But as all my DateTime entity attributes are nullable in my database, I need these custom methods to contain nullable parameters.

A solution for you is to make a new method called ExpressionBinderHelper.MakeCustomFunctionCall where this method looks somewhat like this

    public static Expression MakeCustomFunctionCall(MemberInfo member, ODataQuerySettings querySettings, params Expression[] arguments)
    {
        Contract.Assert(member.MemberType == MemberTypes.Property || member.MemberType == MemberTypes.Method);
        
        Expression functionCall;
        if (member.MemberType == MemberTypes.Method)
        {
            MethodInfo method = member as MethodInfo;
            if (method.IsStatic)
            {
                functionCall = Expression.Call(null, method, arguments);
            }
            else
            {
                functionCall = Expression.Call(arguments.First(), method, arguments.Skip(1));
            }
        }
        else
        {
            var functionCallArguments = ExtractValueFromNullableArguments(arguments);
            
            functionCall = Expression.Property(functionCallArguments.First(), member as PropertyInfo);
        }

        return functionCall;
    }

I have tested creating this method in a copy of your repository and it will work.

@SirTipzy I see. Do you mind sharing a contribution based on your investigation?

By the way, OData spec has this built-in function at: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_date, did you try to use 'date()' method directly? not use your customized method?

@xuzhg Yes I know of this function, but it does not work in your library. Your library just returns the same datetime value as was passed to the function.

We also have other custom methods, DateOnly was just our most simple one I used as an example.

Yes, I can share a contribution.

@bjelbo You can NOT override the corresponding virtual methods to customize your scenarios?

@bjelbo You can NOT override the corresponding virtual methods to customize your scenarios?

I have done so for FilterBinder, but the same is not possible for ComputeBinder if I am not mistaking. Please correct me if I am wrong.

@xuzhg I am still very much interested in getting some clarification on this bug. Also I have left a comment for you on the pull request I am still waiting for a reply on.

@xuzhg @KenitoInc This is still an issue which I really hope will be resolved. Locally I have tested my fix in PR #1090 thoroughly and it works as intended. @xuzhg I have a comment on your comment in the PR. Your comment in the PR "MakeFunctionCall does MORE than MakeCustomFunctionCall. So, it's enough and safe to change using MakeCustomFunctionCall?" From my tests is that custom function calls are applied after querying the database, and therefore, the MakeCustomFunctionCall does less than MakeFunctionCall.

@bjelbo Can you share the working code for CustomFunctions. I also have same use case #1229

@rbalagangadharan I have this PR for it that fixes the issue. Though I have not had the time to create the unit tests they are asking.
#1090

@xuzhg Is there a status regarding this bug?

@xuzhg see PR #1374