Sage 100

forms not available in lookup (5.0 Premium) but they exist in the back end and if you type the form name it finds it and previews/prints. I've added several new forms - funny thing is if you print to the form it keeps it as the default but still does not show up in the lookup. I'm thinking I've seen this before but can't find any write ups.

You might want to check MAS_System\SY_ReportSetting.m4t or SY_ReportOption.m4t or SY_LastFormUsed.m4t. I know there should be records in each of them. Also, do you see them in Report Manager? Sorry, didn't notice it was Premium. Not sure if that makes a difference.

I have seen this exact issue (in Advanced 4.x). Check the files mentioned by Therese. In my case I think I had to create new forms to get them to work right.

I ran into this a couple of weeks ago when doing an upgrade to Sage 100 Advanced v5. I did the same thing - keyed in the form name - and once we printed each form the first time, it retained the settings.

Delete the form reference record found in the SY_ReportSetting file through DFDM. Run the embedded io script for all modules in the affected company. If Crystal was installed from the Productivity Tools reinstall it from the Crystal folder that unpacked from the ISO file. Printing performance is impacted when font MS San Sherif is used, if this issue is present use Arial font type.

thanks everyone - I've definitely got a few things to try. Will post here when i get it resolved.

@EricAnderson reinitialize the SY_reportingsetting - do not delete within SQL - you can make a copy of the table to know the data but reinitialize inside Sage 100. Had the same problem

that worked @Johnny - thanks!

Eric, were you able to insert the old rows back into the table and get the report settings to return or did you have to set the forms back up manually?

we've just been adding them back manually - I don't see a VI job for that and they don't have a ton

I had thought you might just be able to insert the rows back in but I don't know where else they get populated. I will run a SQL trace one of these days to find out, just for curiosity sake. There must be some other table involved to have this issue come up.

@SamanthaKnigge Found it! check out Johnny's solution above. We will give this a shot.

@KarenOLane, this resolved the issue!

@MichelleNichols - Such a memory!!!! Excellent

@JohnnyPabian I'm having a similar issue now with another customer, but it's only the Company Code lookup. What table would be behind that? I assume SY_Company, but thought I'd ask you first. :)

@SamanthaKnigge are they completely blank? Did you try this? https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=20379&sliceId=2&cmd=displayKC&dialogID=18690&docType=kc&isLoadPublishedVer=&stateId=18706&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Is there a blank company code in Company Maintenance? If so, delete it.