callback never fired while Normal save with sync calls work fine. .html is Async method and need Promise to be fulfilled to Move to next render Portions of pdf. I tried native js locally on Browser works fine with callbacks
import html2canvas from 'html2canvas';
import { jsPDF } from "jspdf";
public updateView(context: ComponentFramework.Context<IInputs>): void {
if (params.fileName.raw?.startsWith('yes')) {
params.fileName.raw = 'no'
console.log("pcf fired");
const doc = new jsPDF();
var width = doc.internal.pageSize.getWidth();
var height = doc.internal.pageSize.getHeight();
doc.setFontSize(40);
doc.text("Sample Header", 10, 10);
doc.line(width / 4, height / 4, width, height / 4);
doc.html(document.body, {
html2canvas: {
logging: true
},
callback: (doc) => {
doc.save();
}
}
}
{
"name": "pcf-project",
"version": "1.0.0",
"description": "Project containing your PowerApps Component Framework (PCF) control.",
"scripts": {
"build": "pcf-scripts build",
"clean": "pcf-scripts clean",
"rebuild": "pcf-scripts rebuild",
"start": "pcf-scripts start",
"refreshTypes": "pcf-scripts refreshTypes"
},
"dependencies": {
"@types/react": "^17.0.38",
"@types/react-dom": "^17.0.11",
"dompurify": "2.0.12",
"html2canvas": "1.0.0-rc.2",
"jspdf": "2.5.1",
"react": "^17.0.2",
"react-dom": "^17.0.2"
},
"devDependencies": {
"@types/node": "^16.4",
"@types/powerapps-component-framework": "^1.3.0",
"@typescript-eslint/eslint-plugin": "^4.29.0",
"@typescript-eslint/parser": "^4.29.0",
"eslint": "^7.32.0",
"eslint-config-standard": "^16.0.2",
"eslint-plugin-import": "^2.23.4",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^5.1.0",
"pcf-scripts": "^1",
"pcf-start": "^1",
"typescript": "^4.3"
}
}
Hi @balumallisetty ,
Not sure about the callback issue, and I think it should work since the Field Service Report PCF does the same: https://docs.microsoft.com/en-us/dynamics365/field-service/mobile-powerapp-reporting?WT.mc_id=BA-MVP...
export const printDocument = (onSave) => async () => {
const input = document.getElementById("divToPrint");
let pdf = new jsPDF("p", "pt", "a4");
pdf.setProperties({
title: "PDF Title",
subject: "PDF Sample",
author: "Microsoft",
keywords: "generated, javascript",
creator: "Microsoft",
});
pdf.setLanguage("en");
// Can also add font files here
// pdf.addFileToVFS("chinese.ttf", font);
// pdf.addFont("chinese.ttf", "chinese", "normal");
// pdf.setFont("chinese", "normal");
pdf.html(input, {
callback: (htmlPDF) => {
// Can trigger a download directly to device
// htmlPDF.save("test.pdf");
// Save pdf to timeline/notes
let data = htmlPDF.output("datauristring");
onSave(data);
},
});
};
But maybe it's another issue, which cause the problem.
The "param" is the one from context? If so, you shoudn't try to set the ".raw" value.
The updateView could be called a few times. The async process from pdf.html could take longer, and not be ended until the updateView is called again.
@DianaBirkelbach Thanks for the information. and Sharing the sample PCF
I did try to export PDF from the Component Init() method itself but no luck.
I also Tried same version as Field Service PCF jspdf and html2canvas still callback never gets fired.
Is it possible to find how html2canvas was imported inside the PCF? one of the Blogs I have seen html2canvas imported and Typecased as Below :
Reference : https://github.com/ritikaagarwal08/Screenshot/blob/master/src/screenshot/index.ts
import * as html2canvasWrong from "html2canvas"
var html2canvas = html2canvasWrong as any as (element: HTMLElement, options?: Partial<html2canvasWrong.Options>) => Promise<HTMLCanvasElement>
************************************************************************************************
import { IInputs, IOutputs } from "./generated/ManifestTypes";
import { jsPDF } from "jspdf";
export class pcf implements ComponentFramework.StandardControl<IInputs, IOutputs> {
private _value: number;
private _notifyOutputChanged: () => void;
// private labelElement: HTMLLabelElement;
// private inputElement: HTMLInputElement;
private container: HTMLDivElement;
private _context: ComponentFramework.Context<IInputs>;
private _refreshData: EventListenerOrEventListenerObject;
private _edtorplaceholder: HTMLDivElement;
private isrendered: boolean;
//private editor : editorJS;
public init(context: ComponentFramework.Context<IInputs>, notifyOutputChanged: () => void, state: ComponentFramework.Dictionary, container: HTMLDivElement): void {
this._context = context;
this.container = container;
this._notifyOutputChanged = notifyOutputChanged;
this._refreshData = this.refreshData.bind(this);
//this._value = context.parameters.controlValue.raw!;
const gridHTML = `
<div id="dashboard">
<button id="save-button">Download</button>
`
let ele = document.createElement("div");
this.container = document.createElement("div");
this.container.id = 'GridContainer';
this.container.innerHTML = gridHTML;
//ReactDOM.render(React.createElement(new editorJS(), null), this.container);
this.exportToPDF("");
container.appendChild(this.container);
}
public refreshData(evt: Event): void {
// this._value = (this.inputElement.value as any) as number;
// this.labelElement.innerHTML = this.inputElement.value;
this._notifyOutputChanged();
}
public updateView(context: ComponentFramework.Context<IInputs>): void {
// storing the latest context from the control.
//this._value = context.parameters.controlValue.raw!;
this._context = context;
var params = context.parameters;
if (params.fileName.raw?.startsWith('yes') && (this.isrendered !== true)) {
console.log("pcf fired");
this.isrendered = true;
return;
}
}
public getOutputs(): IOutputs {
return {
//controlValue: this._value
};
}
public pdfReady(doc: any): void {
}
public destroy(): void {
// this.inputElement.removeEventListener("input", this._refreshData);
}
public delay(ms: number) {
return new Promise(resolve => setTimeout(resolve, ms));
}
public exportToPDF(data: string) {
try {
//window["html2canvas"] = html2canvas;
const doc = new jsPDF();
var width = doc.internal.pageSize.getWidth();
var height = doc.internal.pageSize.getHeight();
doc.setFontSize(40);
doc.text("Sample Header", 10, 10);
doc.line(width / 4, height / 4, width, height / 4);
console.log("html method called!");
doc.html(`<!DOCTYPE html>
<html>
<body>
<h2>Text input fields</h2>
<p>Note that the form itself is not visible.</p>
<p>Also note that the default width of text input fields is 20 characters.</p>
</body>
</html>
`, {
callback: (doc) => {
console.log("html is getting Called Back..!");
doc.save();
}
}
);
//doc.save();
} catch (error) {
console.log(error);
}
}
}
@DianaBirkelbach /@ben-thompson / @srasmussen
Could you assist with Above question?
I posted Tagging #jspdf in stackoverflow, https://stackoverflow.com/q/73095905/4491572. Looks Issue is with PCF and JSPDF combination
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages