Printing to Doxcycle from Taxcycle

DoxCycle
1

With the new version of Doxcycle I have not been able to print to it from Taxcycle.

Has anyone else been able to? Just wondering if it something in my own setup or if it the new version’s problem?

2

Draging and dropping an email with a attached pdf file does not seem to work for me any longer either.

3

Thank you Arliss, the team will look into this and we will report back!

4

No problem here…TC version 13.2.53840.0 and DC 13.1.52818.0.

5

New version

DoxCycle 13.2.53908.0—.NET 6 Upgrade

6

Can you please confirm if you on Windows 11 with the most recent TaxCycle version?

Could you please check if you have detailed logging selected in your DoxCycle options (and TaxCycle in case there is an issue there), retrace the actions you noted here and send logs to us at info@taxcycle.com ? Please tag me in the email.

7

Yes to all questions.

Error for the printing to Doxcycle is clipped below.
There is no error generated for the drag and drp - just nothing happens.

Title: Well, this is embarrassing
Message: DoxCycle has encountered an unexpected problem and was unable to complete this task.

Please call **1-888-841-3040** for assistance with this error.
Details: DoxCycle 13.2.53908.0

System.NullReferenceException Object reference not set to an instance of an object.
Source : Trilogy.Extensibility
at Trilogy.Extensibility.DocumentLink.MapToProto(DocumentLink documentLink, Dictionary2 mappedObjects) at Trilogy.Extensibility.ApplicationLink.MapToProto(ApplicationLink applicationLink, Dictionary2 mappedObjects)
at Trilogy.Document.Core.File.RecognitionForceInfo.op_Implicit(RecognitionForceInfo recognitionForceInfo)
at Trilogy.Document.Service.Client.DocumentServiceClient.RecognizeAsync(CancellationToken cancellationToken)
at Trilogy.Document.Manager.ViewModel.MainWindowViewModel.CreateClient(String file, ImportEventInfo info, Boolean isTempFile, RecognitionForceInfo forceInfo, WorkgroupOptions workgroupOptions)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Stack Frames:
{
	 [06000A51] [L_000000AA]	at Trilogy.Extensibility.dll, Trilogy.Extensibility.DocumentLink::MapToProto
	 [06000B02] [L_0000009E]	at Trilogy.Extensibility.dll, Trilogy.Extensibility.ApplicationLink::MapToProto
	 [060001A3] [L_0000003C]	at Trilogy.Document.Core.File.dll, Trilogy.Document.Core.File.RecognitionForceInfo::op_Implicit
	 [060001F8] [L_000000EF]	at Trilogy.Document.Service.Client.dll, Trilogy.Document.Service.Client.DocumentServiceClient+<RecognizeAsync>d__68::MoveNext
	 [06003AFC] [L_00000011]	at System.Private.CoreLib.dll, System.Runtime.ExceptionServices.ExceptionDispatchInfo::Throw
	 [060050CB] [L_00000037]	at System.Private.CoreLib.dll, System.Runtime.CompilerServices.TaskAwaiter::ThrowForNonSuccess
	 [060050CA] [L_00000028]	at System.Private.CoreLib.dll, System.Runtime.CompilerServices.TaskAwaiter::HandleNonSuccessAndDebuggerNotification
	 [06001935] [L_0000034F]	at DoxCycle.dll, Trilogy.Document.Manager.ViewModel.MainWindowViewModel+<CreateClient>d__320::MoveNext
	 [06003AFC] [L_00000011]	at System.Private.CoreLib.dll, System.Runtime.ExceptionServices.ExceptionDispatchInfo::Throw
	 [0600335A] [L_00000000]	at System.Private.CoreLib.dll, System.Threading.Tasks.Task+<>c::<ThrowAsync>b__128_0
	 [06000EB8] [L_00000000]	at WindowsBase.dll, System.Windows.Threading.ExceptionWrapper::InternalRealCall
	 [06000EB7] [L_0000003A]	at WindowsBase.dll, System.Windows.Threading.ExceptionWrapper::TryCatchWhen
}
8

Thanks @Arliss - our team has been able to replicate the bugs you noted and engineering is investigating. Will update you when I have a timeline for a patch.

1 Like
9

You might as well add the default file location for the 2024 files to the update.

2 Likes
10

Curious. I’m running on WinServer 2016 as a base and I expect that .NET6 hasn’t been pushed out to it. I’m still on 4.8.

11

The current release needs a full install. You can grab the update from our website.

12

Ah – K – thanks; will do.

13

yes please. Especially for T2. Should have that as soon as Jan 01 hits each year at the least.

14

Arliss, a little off topic but what are you printing from Taxcycle to Doxcycle? I suspect I am not using software best practices. My doxcycle has basically the client slips and receipts

Thanks

15

Just a backup copy of the return as filed.

16

We have a patch ready and in final testing that addresses the above reported issues. Looks like it will be ready to be released tomorrow.